PM03457: A performance improvement for marshaling of JAX-WS, WESB and WPS web service messages.

Fixes are available

APAR status

Closed as program error.

Error description

A WebSphere Enterprise Service Bus (WESB) mediation reads a
web service message and delegates it to the next node without
querying the contents of the message.   Sometimes this
scenario requires more time than a mediation that actually
processes the web service message.

The WESB component uses the WebSphere Process Server and
the JAX-WS runtime to process these web service messages.  The
slow performance is due to the algorithms with the JAX-WS
runtime.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server users of   *
*                  WebSphere Enterprise Service Bus, WebSphere *
*                  Process Server or JAX-WS                    *
****************************************************************
* PROBLEM DESCRIPTION: Slower than expected marshaling of      *
*                      web service messages when using         *
*                      WebSphere Enterprise Service Bus,       *
*                      WebSphere Process Server or JAX-WS      *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR      *
****************************************************************
A WebSphere Enterprise Service Bus (WESB) mediation reads a
web service message and delegates it to the next node without
querying the contents of the message.   Sometimes this
scenario requires more time than a mediation that actually
processes the web service message.

The WESB component uses the WebSphere Process Server and the
JAX-WS runtime to process these web service messages.  The
slow performance is due to the algorithms with the JAX-WS
runtime.

This scenario can be detected by examining the trace
log.
   A) look for an OMSourcedElement.forceExpand method
   B) look for an ancestor call to the
      StreamingOMSerializer.serializeNode method

Example:

[03/12/09 10:16:13:156 GMT] 000008b5 ParsedEntityD 1
org.apache.axis2.jaxws.context.listener.ParsedEntityDataSource$D
ata readParsedEntityStream call stack:DEBUG_FRAME =
org.apache.axis2.jaxws.context.listener.ParsedEntityDataSource$D
ata.readParsedEntityStream(ParsedEntityDataSource.java:360)

 DEBUG_FRAME =
org.apache.axis2.jaxws.context.listener.ParsedEntityDataSource.g
etReader(ParsedEntityDataSource.java:172)

 DEBUG_FRAME =
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getDirectRead
er(OMSourcedElementImpl.java:220)

 DEBUG_FRAME =
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.forceExpand(O
MSourcedElementImpl.java:243)

 DEBUG_FRAME =
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getFirstOMChi
ld(OMSourcedElementImpl.java:899)

 DEBUG_FRAME =
org.apache.axiom.om.impl.llom.OMNavigator._getFirstChild(OMNavig
ator.java:142)

 DEBUG_FRAME =
org.apache.axiom.om.impl.llom.OMNavigator.updateNextNode(OMNavig
ator.java:114)

 DEBUG_FRAME =
org.apache.axiom.om.impl.llom.OMNavigator.next(OMNavigator.java:
97)

 DEBUG_FRAME =
org.apache.axiom.om.impl.llom.OMStAXWrapper.updateNextNode(OMStA
XWrapper.java:1096)

 DEBUG_FRAME =
org.apache.axiom.om.impl.llom.OMStAXWrapper.updateLastNode(OMStA
XWrapper.java:1087)

 DEBUG_FRAME =
org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.j
ava:1003)

 DEBUG_FRAME =
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.seriali
zeNode(StreamingOMSerializer.java:125)

Problem conclusion

The JAX-WS runtime stores certain parts of the message in a
small, optimized form.  In some scenarios a utility,
StreamingOMSerializer, writes out the web service message.
The StreamingOMSerializer algorithm causes the optimized
message to be expanded into a large number of Java objects.
This expansion and subsequent garbage collection is the root
cause of the slow performance.

The StreamingOMSerializer algorithm is changed to recognize
the optimized form of the message and avoid its expansion.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.9.  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
PM03457
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-12-14
Closed date
2010-01-05
Last modified date
2010-01-05

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

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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:
24 October 2021

Tips

PM03457: A performance improvement for marshaling of JAX-WS, WESB and WPS web service messages.

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

Document Information

Share your feedback

Need support?