Fixes are available
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
When you run JAX-RPC client under heavy load you might experience a performance degradation problem or server hang. A symptom of this problem can be seen in the javacore file. The user may notice a number of threads blocked within the com/ibm/ws/webservices/engine/MessageContext.setPort method. Here is an example: "WebContainer : 00002" (TID:0x000000002EBF0E00, sys_thread_t:0x0000000025D2D630, state:B, native ID:0x00000000000044B4) prio=5 at com/ibm/ws/webservices/engine/MessageContext.setPort(MessageCont ext.java:799(Compiled Code)) at com/ibm/ws/webservices/engine/MessageContext.setTargetPort(Messa geContext.java:760(Compiled Code)) at com/ibm/ws/webservices/engine/client/Connection.invoke(Connectio n.java:590(Compiled Code)) at com/ibm/ws/webservices/engine/client/Connection.invoke(Connectio n.java:495(Compiled Code)) at com/ibm/ws/webservices/engine/client/Stub$Invoke.invoke(Stub.jav a:977(Compiled Code)) at some_Web_Services_Client_Code ...
Local fix
N/A.
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V6.1 and * * V7.0 users of JAX-RPC * **************************************************************** * PROBLEM DESCRIPTION: Excessive object locking in the * * JAX-RPC runtime during heavy load may * * cause a performance degradation or * * apparent server hang * **************************************************************** * RECOMMENDATION: Install a fix pack containing this APAR. * **************************************************************** When you run many (100+) JAX-RPC clients in the same JVM, you might experience a performance degradation problem or apparent server hang. A symptom of this problem can be seen in the javacore file. You may notice a number of threads blocked within the com/ibm/ws/webservices/engine/MessageContext.setPort method. Here is an example: "WebContainer : 00002" (TID:0x000000002EBF0E00, sys_thread_t:0x0000000025D2D630, state:B, native ID:0x00000000000044B4) prio=5 at com/ibm/ws/webservices/engine/MessageContext.setPort(MessageCont ext.java:799(Compiled Code)) at com/ibm/ws/webservices/engine/MessageContext.setTargetPort(Messa geContext.java:760(Compiled Code)) at com/ibm/ws/webservices/engine/client/Connection.invoke(Connectio n.java:590(Compiled Code)) at com/ibm/ws/webservices/engine/client/Connection.invoke(Connectio n.java:495(Compiled Code)) at com/ibm/ws/webservices/engine/client/Stub$Invoke.invoke(Stub.jav a:977(Compiled Code)) at some_Web_Services_Client_Code ...
Problem conclusion
The JAX-RPC runtime must synchronize access to common data structures. A performance degradation or apparent server hang may occur if too much processing is done with a synchronized block. This will cause the other threads to wait for access. The JAX-RPC runtime code associated with the MessageContext.setPort method is changed to reduce the amount of processing within the synchronized block. The code has also been improved to limit the number of synchronized blocks. These changes improve performance. The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.37 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
PM24289
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-10-11
Closed date
2010-12-06
Last modified date
2010-12-06
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
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
Document Information
Modified date:
24 October 2021