PM19866: A WSWS3250E ERROR MAY OCCUR WHEN A JAX-RPC APPLICATION TRIES TO DESERIALIZE A MESSAGE WITH AN AXIS-STYLE ATTACHMENT.

6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• When a JAX-RPC application tries to deserialize a SOAP message
  with an Axis-style attachment, the following exception may be
  observed in the JVM log:
  
  [8/4/10 0:27:20:305 MDT] 00000024 WebServicesSe E
  org.apache.commons.logging.impl.Jdk14Logger error WSWS3227E:
  Error: Exception:
  WebServicesFault
  faultCode:
  {http://schemas.xmlsoap.org/soap/envelope/}Server.generalExcepti
  on
  faultString: java.lang.RuntimeException: WSWS3250E: Error:
  AttachmentUtils.getActiviationDataHandler received a null
  parameter as a part.WebServicesFault
  faultCode:
  {http://schemas.xmlsoap.org/soap/envelope/}Server.generalExcepti
  on
  faultString: WSWS3250E: Error:
  AttachmentUtils.getActiviationDataHandler received a null
  parameter as a part.
  faultActor: null
  faultDetail:
  
  WSWS3250E: Error: AttachmentUtils.getActiviationDataHandler
  received a null parameter as a part.
  at
  com.ibm.ws.webservices.engine.attachments.AttachmentUtils.getAct
  ivationDataHandler(AttachmentUtils.java:125)
  at
  com.ibm.ws.webservices.engine.encoding.ser.JAFDataHandlerDeseria
  lizer.getDataHandler(JAFDataHandlerDeserializer.java:174)
  at
  com.ibm.ws.webservices.engine.encoding.ser.JAFDataHandlerDeseria
  lizer.makeValue(JAFDataHandlerDeserializer.java:154)
  at
  com.ibm.ws.webservices.engine.encoding.ser.SimpleDeserializer.on
  EndElement(SimpleDeserializer.java:239)
  at
  com.ibm.ws.webservices.engine.encoding.Deserializer.endElement(D
  eserializer.java:675)
  ...
  
  This can happen on either the client or service.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of JAX-RPC applications in IBM        *
  *                  WebSphere Application Server V6.1           *
  ****************************************************************
  * PROBLEM DESCRIPTION: A WSWS3250E error may occur when a      *
  *                      JAX-RPC application tries to            *
  *                      deserialize a message with an           *
  *                      Axis-style attachment.                  *
  ****************************************************************
  * RECOMMENDATION:  Install a fixpack that includes this APAR.  *
  ****************************************************************
  When a JAX-RPC application tries to deserialize a SOAP message
  with an Axis-style attachment, the following exception may be
  observed in the JVM log:
  
  [10/06/24 16:55:08:796 JST] 0000002b MCUtils
  com.ibm.ws.webservices.engine.utils.MCUtils
  interceptDeserializationException
  interceptDeserializationException:
  java.lang.RuntimeException: WSWS3250E: Error:
  AttachmentUtils.getActiviationDataHandler received a null
  parameter as a part.WebServicesFault
  faultCode:
  {http://schemas.xmlsoap.org/soap/envelope/}
  Server.generalException
  faultString: WSWS3250E: Error:
  AttachmentUtils.getActiviationDataHandler received a null
  parameter as a part.
  faultActor: null
  faultDetail:
  
  WSWS3250E: Error: AttachmentUtils.getActiviationDataHandler
  received a null parameter as a part.
  at com.ibm.ws.webservices.engine.attachments.AttachmentUtils.
  getActivationDataHandler(AttachmentUtils.java:125)
  at com.ibm.ws.webservices.engine.encoding.ser.
  JAFDataHandlerDeserializer.
  getDataHandler(JAFDataHandlerDeserializer.java:174)
  at com.ibm.ws.webservices.engine.encoding.ser.
  JAFDataHandlerDeserializer.
  makeValue(JAFDataHandlerDeserializer.java:154)
  at com.ibm.ws.webservices.engine.encoding.
  ser.SimpleDeserializer.
  onEndElement(SimpleDeserializer.java:239)
  at com.ibm.ws.webservices.engine.encoding.Deserializer.
  endElement(Deserializer.java:675)
  ...
  
  This can happen on either the client or service.
  
  The following is an example of a SOAP message with an
  Axis-style attachment:
  
  <soapenv:Envelope
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
           <soapenv:Body>
              <p935:attachment
  xmlns:p935="http://example.ibm.com">
                    <dataHandler
  href="cid:dataHandler=19620176631.1278648856640.IBM.WEBSERVICES@
  examplehost"/>
  ...
  
  ------=_Part_0_1801349982.1278648856656
  Content-Type: application/octet-stream
  Content-Transfer-Encoding: binary
  Content-Id:
  
  <dataHandler=19620176631.1278648856640.IBM.WEBSERVICES@exampleho
  st>
  ...
  
  The element in the root part (SOAP Envelope) has an href
  attribute (in the above example, that element is
  "dataHandler"); the value of the href corresponds to the
  value of the Content-ID header in the MIME part, which
  represents the attachment. These characteristics are what make
  this attachment Axis-style.
  

Problem conclusion

• The JAX-RPC runtime was changed to properly deserialize
  Axis-style attachments.
  
  This same fix is included in V7 under APAR PM18083.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.35.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP