IBM Support

PI33437: ON ERROR PREVIOUS SOAP PART IS NOT CLEARED AND IS SENT OUT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When MTOM is enabled, a web service response contains two main
    parts, one is a SOAP part (SOAP envelope), the other is an
    attachment  part. In some scenarios, an error happened during
    attachment writing. At that time, the buffer used for the SOAP
    part is already flushed to the output stream. Then when the
    web service engine tris to handle the exception and send a
    SOAPFault to the same output stream, the previous SOAP part is
    not cleared. As a result you will see a half-written
    attachment part followed by a complete SOAP fault in a TCP
    trace.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  JAX-WS web services with MTOM enabled.      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When an exception occurrs during        *
    *                      attachment writing in a SOAP response,  *
    *                      the SOAP fault envelope can not be      *
    *                      received.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This occurs because the web service engine writes the SOAP
    part and attachment part of a response message separately.
    When an exception occurrs while writing attachment part, the
    SOAP part has already been written to the buffer and flushed.
    In this APAR, when the exception is caught, resetBuffer will
    be called to clean up the original SOAP part. However,
    resetBuffer only works before the content is written to the
    output stream, after which, resetBuffer does not work.
    

Problem conclusion

  • A new property com.ibm.ws.websvcs.ResetBuffer=true is added to
    the WebSphere Application Server to allow a user to reset the
    buffer when an exception happens during attachment writing.
    The default value of this property is false.
    
    The following Knowledge Center topic describes how to set a
    JVM property:
    http://www-
    01.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphe
    re.base.doc/ae/xrun_jvm.html?
    cp=SSEQTP_8.5.5%2F1-17-5-387&lang=en
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.6.  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 number

    PI33437

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-01-26

  • Closed date

    2015-04-08

  • Last modified date

    2015-04-08

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022