PM03728: PERFORMANCE DEGRADATION WHEN MIGRATING A JAX-RPC DII APPLICATION FROM V5.1

Fixes are available

APAR status

Closed as program error.

Error description

When an administrator migrated a JAX-RPC application from
WebSphere Application Server V5.1, he noticed a slight
performance degradation.

The JAX-RPC application constructs a JAX-RPC Dynamic
Invocation Interface (DII).  The application uses the DII to
invoke the web service a single time, and then the application
discards the DII.

The DII invocation required an additional 300ms when the
application was installed on WebSphere Application Server V6.1.

The solution for this APAR may also help to resolve slower than
expected performance when a Web Service request is sent to a
WebSphere Process Server (WPS) mediation module.  The amount of
time spent in the mediation module may increase from less than 1
second to about 6 seconds, and the CPU utilization of the
application may also increaseo.  A Web Services engine trace
shows delays occurring in the
com.ibm.ws.webservices.engine.client.Call.loadOperationFromWSDL
method.

Local fix

1) Create a JAX-RPC Call object.
2) Reuse that same Call object for multiple invocations.

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V6.1 and   *
*                  V7.0 users of JAX-RPC Dynamic Invocation    *
*                  Interface (DII)                             *
****************************************************************
* PROBLEM DESCRIPTION: Small performance degradation           *
*                      observed when migrating a JAX-RPC DII   *
*                      application from V5.1.                  *
****************************************************************
* RECOMMENDATION:  If a JAX-RPC DII invokes the same remote    *
*                  web service operation multiple times, then  *
*                  the JAX-RPC application should create a     *
*                  single DII Call object and use it multiple  *
*                  times.                                      *
****************************************************************
When an administrator migrated a JAX-RPC application from
WebSphere Application Server V5.1, he noticed a slight
performance degradation.
The JAX-RPC application constructs a JAX-RPC Dynamic
Invocation Interface (DII).  The application uses the DII to
invoke the web service a single time, and then the application
discards the DII.
The DII invocation required an additional 300ms when the
application was installed on WebSphere Application Server V6.1.
The administrator noticed this problem because the application
invokes the web service thousands of times.  Each time the
application constructs a new DII Call object.  This is not a
best practice.  Instead the application should create a single
DII Call object and use it for successive invocations.

Problem conclusion

The JAX-RPC runtime initializes state information on the DII
Call object when it is first used.   In WebSphere Application
Server V6 and V7, the WSDL file is processed as part of this
initialization.  The WSDL file processing is necessary to
ensure that the state information is correct.  The performance
difference between V5.1 and V6/V7 is due to this extra WSDL
processing.

A new JVM property is added to allow a V6 or V7 administrator
to disable this extra WSDL processing.

JVM Property Name:
com.ibm.ws.webservices.jaxrpc.call.disable.wsdl.processing
Values: false (default) and true

If this property is set to true, the WSDL processing is
disabled within the JAX-RPC DII Call object.

Note: Disabling the WSDL processing might result
in hard to find errors so is discouraged unless the
performance effects cannot be tolerated. In most cases, the
performance difference is very small and will likely have
little or no impact for most customers. When used, it should
be done with caution, and reversed if errors appear.

IBM understands there may be customers with a large number of
V5.1 applications.  Some of these customers may not have the
authority or ability to modify the application code to use the
best practice (reuse DII Call objects).


Additional information on how to set a JVM custom property is
available in the "Java virtual machine custom properties"
topic in the IBM Information center.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.31 and 7.0.0.11.  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
PM03728
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
2009-12-16
Closed date
2010-01-05
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
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:
29 December 2021

Tips

PM03728: PERFORMANCE DEGRADATION WHEN MIGRATING A JAX-RPC DII APPLICATION FROM V5.1

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?