PI30166: OUTGOING WEB SERVICE REQUEST IS MISSING THE CLOSING MIMEBOUNDARY TAG.

8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
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.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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

• Customer has a module that accepts a web service request and
  makes a web service call after going through a mediation
  component.
  When the client making the initial call has MTOM enabled, the
  final outgoing web service request is missing the closing
  MIMEBoundary tag.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application server users of   *
  *                  JAX-WS web services applications            *
  ****************************************************************
  * PROBLEM DESCRIPTION: When the client making the initial      *
  *                      call has MTOM enabled, the final        *
  *                      outgoing web service request may miss   *
  *                      the closing MIMEBoundary tag.           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The final outgoing web service request may miss the closing
  MIMEBoundary tag when a webservice client have a handler which
  adds some headers in outbounding request.
  

Problem conclusion

• The problem is fixed by addition of SoapHeader serialization,
  please note: the followingjvm property must be added
  "com.ibm.webservice.KeepSoapHeaderHighFidelity=true" in the
  jvm and Application Server must be restarted. to make the fix
  take effect.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.5.5.6 and 8.0.0.11.  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

• R800 PSY

     UP

• R850 PSY

     UP