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

Fixes are available

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

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

Document Information

Modified date:
27 October 2021

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?