PI28681: PARSEEXCEPTION DURING PROCESSING WEBSERVICE WITH MTOM REQUEST WITH A SPACE OR CRLF BEFORE XOP:INCLUDE ELEMENT

8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• When there are some spaces between the <XOP:INCLUDE and its
  parent element <prefix:AttachmentData64Binary> in the inbound
  HTTP SOAP request with MTOM attachment/s received by the
  JAX-WS Web Services provider then the AXIOM parser will not
  parse the inbound SOAP request properly.
  .
  Here is an example of javax.xml.stream.XMLStreamException
  exception that might be recorded in WebSphere logs:
  ---------------------------
  ...
  [9/24/14 14:18:04:103 EDT] 000000ad SystemErr     R
  javax.xml.stream.XMLStreamException: Expected xop:Include as the
  sole child of an element information item (see section 3.2 of
  http://www.w3.org/TR/xop10/)
  [9/24/14 14:18:04:104 EDT] 000000ad SystemErr     R    at
  org.apache.axiom.util.stax.xop.XOPDecodingStreamReader.next(XOPD
  ecodingStreamReader.java:209)
  [9/24/14 14:18:04:104 EDT] 000000ad SystemErr     R    at
  org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOM
  Builder.java:675)
  [9/24/14 14:18:04:104 EDT] 000000ad SystemErr     R    at
  org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilde
  r.java:214)
  [9/24/14 14:18:04:104 EDT] 000000ad SystemErr     R    at
  org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OME
  lementImpl.java:338)
  [9/24/14 14:18:04:104 EDT] 000000ad SystemErr     R    at
  org.apache.axiom.om.impl.traverse.OMChildrenIterator.next(OMChil
  drenIterator.java:112)
  [9/24/14 14:18:04:104 EDT] 000000ad SystemErr     R    at
  org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OM
  ElementImpl.java:954)
  [9/24/14 14:18:04:105 EDT] 000000ad SystemErr     R    at
  org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSeriali
  ze(SOAPEnvelopeImpl.java:230)
  [9/24/14 14:18:04:105 EDT] 000000ad SystemErr     R    at
  org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSer
  ializableImpl.java:134)
  [9/24/14 14:18:04:105 EDT] 000000ad SystemErr     R    at
  org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSer
  ializableImpl.java:115)
  [9/24/14 14:18:04:105 EDT] 000000ad SystemErr     R    at
  org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSer
  ializableImpl.java:141)
  [9/24/14 14:18:04:105 EDT] 000000ad SystemErr     R    at
  org.apache.axis2.jaxws.message.impl.MessageImpl.getAsSOAPMessage
  (MessageImpl.java:208)
  [9/24/14 14:18:04:105 EDT] 000000ad SystemErr     R    at
  org.apache.axis2.jaxws.handler.SoapMessageContext.getMessage(Soa
  pMessageContext.java:183)
  [9/24/14 14:18:04:105 EDT] 000000ad SystemErr     R    at
  com.applicationHandler.handleMessage(Unknown Source)
  ...
  

Local fix

• M/A.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server users of   *
  *                  JAX-WS web services                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: A parse exception is thrown when        *
  *                      demarshalling the first JAX-WS request  *
  *                      with optimized MTOM attachments after   *
  *                      Application Server restart.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During the demarshalling the JAX-WS request, if a space or
  other character is found before or after optimized MTOM
  element, this will be treated as envidence that it's not a
  correct MTOM element. Since per specification, there should no
  other contents between MTOM element and its parent, a parse
  exception will be thrown.
  

Problem conclusion

• This APAR has changed WebSphere Application Server to tolerate
  the space, tab or line break.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.5.  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP