IBM Support

PM40220: A SOAP message with attachment may not be marshalled in MTOM format if a JAX-WS SOAP handler intercepts it.

Fixes are available

7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A JAX-WS application may implement a SOAP handler, intercept
    the outbound message, and call
    javax.xml.ws.handler.soap.SOAPMessageContext.setMessage(). The
    outbound SOAP with attachment message may not be marshalled
    in the MTOM format, even though the application has enabled
    MTOM.
    
    For example, the outgoing message may be observed in the SwA
    format:
    
    <attachment_inf>UEsDBAoAAAAAABZhjz2+.....AAAAA==...
    </attachment_inf>
    
    Where the attachment is embedded in the SOAP envelope.
    
    But the expected format should be in MTOM, shown below:
    
    <attachment_inf><xop:Include href="cid:
    urn:uuid:E96C6038B1ADE473AE1305680478405@apache.org"
    xmlns:xop="http://www.w3.org/2004/08/xop/include"/>
    </attachment_inf>
    
    
    But actual outbound attachment part is sent out as
    "application/soap+xml" content type rather than xop
    content type so we can see the following attachment
    part.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
    *                  V7.0 and V8.0 JAX-WS applications that      *
    *                  implement SOAP handlers and send SOAP with  *
    *                  attachments using MTOM.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: A SOAP with attachment message may      *
    *                      not be marshalled in MTOM               *
    *                      format if a JAX-WS SOAP handler         *
    *                      intercepts it.                          *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack that includes this APAR. *
    ****************************************************************
    A JAX-WS application may implement a SOAP handler, intercept
    the outbound message, and call
    javax.xml.ws.handler.soap.SOAPMessageContext.setMessage(). The
    outbound SOAP with attachment message may not be marshalled
    in the MTOM format, even though the application has enabled
    MTOM.
    
    For example, the outgoing message may be observed in the SwA
    format:
    
    <attachment_inf>UEsDBAoAAAAAABZhjz2+.....AAAAA==...
    </attachment_inf>
    
    Where the attachment is embedded in the SOAP envelope.
    
    But the expected format should be in MTOM, shown below:
    
    <attachment_inf><xop:Include href="cid:
    urn:uuid:E96C6038B1ADE473AE1305680478405@apache.org"
    xmlns:xop="http://www.w3.org/2004/08/xop/include"/>
    </attachment_inf>
    
    For more information on SwA and MTOM formats, see the
    Information Center article "Enabling MTOM for JAX-WS Web
    services" for your operating system and WebSphere Application
    Server version.
    

Problem conclusion

  • The JAX-WS runtime was changed to detect if MTOM is enabled
    when the outbound message is intercepted via a SOAP handler.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.21 and 8.0.0.1.  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

    PM40220

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-05-26

  • Closed date

    2011-06-30

  • Last modified date

    2011-06-30

  • 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

  • R700 PSY

       UP

  • R800 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM40220

Modified date: 30 June 2011