PM31633: A JAX-RPC application cannot process a SOAP attachment whose Content-Id header is missing a part name.

Fixes are available

APAR status

Closed as program error.

Error description

When a WebSphere Application Server JAX-RPC application
receives a SOAP message with an attachment, a
NullPointerException error can occur in the application.

The attachment is mapped to a javax.activation.DataHandler
Java ojbect. The NullPointerException occurs when the
application tries to invoke a method on the object, but it is
null.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  V6.1 and V7.0 JAX-RPC applications that     *
*                  receive SOAP attachments.                   *
****************************************************************
* PROBLEM DESCRIPTION: A JAX-RPC application cannot process    *
*                      a SOAP attachment whose Content-Id      *
*                      header is missing a part name           *
****************************************************************
* RECOMMENDATION:  Install a fix pack that includes this APAR. *
****************************************************************
When a WebSphere Application Server JAX-RPC application
receives a SOAP message with an attachment, a
NullPointerException error can occur in the application.

Note that this APAR applies to the following use case only:

* The attachment is mapped to a javax.activation.DataHandler
Java object.
* The incoming message's attachment part has a Content-Id
header that is missing the part name.

Per the Attachments Profile Version 1.0, an attachment's
Content-Id header must consist of the following:

* The value of the name attribute of the wsdl:part element
referenced by the mime:content.
* The character '=' (0x3D).
* A globally unique value such as a UUID.
* The character '@' (0x40).
* A valid domain name under the authority of the entity
constructing the message.

These requirements can be found at
http://www.ws-i.org/profiles/attachmentsprofile-1.0.html#Value-s
pace_of_Content-Id_Header

For example, given the following WSDL binding:

<wsdl:binding
    ...
    <mime:multipartRelated>
      <mime:part>
        <soapbind:body parts="body" use="literal"/>
      </mime:part>
      <mime:part>
        <mime:content part="helloWorldAttachmentPart"
type="application/octet-stream"/>
      </mime:part>
    </mime:multipartRelated>
    ...
</wsdl:binding>

The resulting Content-Id header should look like this:

Content-ID:
<helloWorldAttachmentPart=2472efa77ba2e0fe-28de1fbb4aa84d@exampl
e.com>

If the header does not follow this format, then the JAX-RPC
runtime will not be able to identify and deserialize the
attachment, resulting in the null javax.activation.DataHandler
object.

Problem conclusion

Toleration code was added to the JAX-RPC runtime so that it
can process the attachment, even though its Content-Id header
is not compliant with the Attachments Profile.

Note that this toleration fix will only work if the
application meets the following criteria:

* The attachment is in WSDL 1.1 style, which is described at
http://www.w3.org/TR/wsdl#_Toc492291084
* In the WSDL message that describes the incoming SOAP
message, there is exactly one MIME part. If the WSDL message
contains more than one MIME part, then this toleration fix
will not work.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.39 and 7.0.0.17.  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
PM31633
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-01-31
Closed date
2011-02-15
Last modified date
2011-02-15

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021

Tips

PM31633: A JAX-RPC application cannot process a SOAP attachment whose Content-Id header is missing a part name.

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?