PH26204: ORG.APACHE.AXIOM.OM.OMEXCEPTION: A DATA HANDLER WAS NOT FOUND

APAR status

• Closed as program error.

Error description

• Web service call fails with the following error when reading and
  marshalling the MTOM attachment data from the response message:
  
  
         [5/28/20 18:03:29:507 EDT] 00000179 ExceptionFact 1
  org.apache.axis2.jaxws.ExceptionFactory logRootCause
  stack:org.apache.axiom.om.OMException: A data handler was not
  found for content id
  cid:5dfaa21e-5376-4f9d-8db8-cdd8bbee1688@http://cxf.apache.org/
  
   at
  org.apache.axis2.datasource.jaxb.AbstractJAXBAttachmentUnmarshal
  ler.getAttachmentAsDataHandler(AbstractJAXBAttachmentUnmarshalle
  r.java:105)
  
   at
  com.ibm.jtc.jax.xml.bind.v2.runtime.unmarshaller.MTOMDecorator.s
  tartElement(MTOMDecorator.java:100)
  
   at
  com.ibm.jtc.jax.xml.bind.v2.runtime.unmarshaller.StAXStreamConne
  ctor.handleStartElement(StAXStreamConnector.java:256)
  
   at
  com.ibm.jtc.jax.xml.bind.v2.runtime.unmarshaller.StAXStreamConne
  ctor.bridge(StAXStreamConnector.java:190)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server users of   *
  *                  JAX-WS Web Services                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: DataHandler error occurs when           *
  *                      retrieving attachment data from SOAP    *
  *                      message                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a tWAS Web services provider processes a SOAP message
  from a Liberty client that contains attachment, it may
  receive the following error:
  apache.axiom.om.OMException: A data handler was not found for
  content id
  cid:569f1001-485e-4cdb-bc47-acfbc80c4fb4@http://cxf.apache.org/
  

Problem conclusion

• This error occurred because the  Web services Axis2 code was
  storing the dataHandler Content ID (cid) in cache with
  non-ascii characters, instead of storing the decoded content
  ID in cache.
  The Web services Axis2 code is modified to decode the
  dataHandler content ID befofe storing it in cache.
  
  The fix for this APAR is targeted for inclusion in fix packs
  8.5.5.18 and 9.0.5.6. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP