PM59793: SOAP Message updates made in a jax-ws handler might be lost.

Fixes are available

APAR status

Closed as program error.

Error description

A change to a SOAPMessage made by a JAX-WS handler might be
lost if the handler calls SoapMessageContext.getMessage()
multiple times before or after changing the message.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server using JAX-WS handlers.               *
****************************************************************
* PROBLEM DESCRIPTION: SOAP Message updates made in a JAX-WS   *
*                      handler might be lost.                  *
****************************************************************
* RECOMMENDATION:  Install a fix pack containing this APAR.    *
****************************************************************
A message that has been updated by a JAX-WS handler appears
correct when dumped in the handler, but when the message is
put on the wire, the change is missing. The problem occurs
when a handler calls getMessage() multiple times.
When handlers are used, JAX-WS transforms an internal message
representation into a SoapMessageContext for use by the
handlers.  This transformation can be expensive so some
caching logic exists to minimize these transformations.  If
SoapMessageContext.getMessage was called multiple times,  it
was possible for a changed message to be lost.

Problem conclusion

The caching logic is revised so the problem no longer
occurs.

This change must be enabled by setting the JVM property
jaxws.handler.reducecaching=true

Use of this JVM property is NOT compatible with modifying SOAP
headers directly through JAX-WS message context properties as
documented at:

http://www14.software.ibm.com/webapp/wsbroker/redirect?version=c
ompass&product=was-nd-dist&topic=rwbs_manipulatesoapjaxwshandler

Using both types of message modification might cause loss of
information.

For information on setting a JVM property see:

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?
topic=/com.ibm.websphere.nd.doc/info/ae/ae/xrun_jvm.html

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.25 and 8.0.0.4  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
PM59793
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
2012-03-06
Closed date
2012-04-18
Last modified date
2012-04-18

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:
28 October 2021

Tips

PM59793: SOAP Message updates made in a jax-ws handler might be lost.

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?