Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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 using WebSphere Process Server JAX-WS web service calls, an OutOfMemoryError or an unresponsive process server can occur.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM WebSphere Process Server * * JAX-WS providers * **************************************************************** * PROBLEM DESCRIPTION: The performance of a WebSphere * * Process Server JAX-WS * * javax.xml.ws.Provider might degrade * * when invoked under high load. * **************************************************************** * RECOMMENDATION: Install a fix pack that includes this APAR. * **************************************************************** The performance of a WebSphere Process Server JAX-WS javax.xml.ws.Provider might degrade when invoked under high load. This occurs when the Service Component Architecture (SCA) component prepares the SOAP response. The problem is due to the way SCA invokes the JAX-WS runtime, resulting in a new namespace prefix created for each namespace URI, as shown in these debug messages: [1/24/11 12:11:16:625 PST] 0000007d OMSerializerU 1 org.apache.axiom.om.impl.util.OMSerializerUtil getNextNSPrefix DEBUG_FRAME = org.apache.axiom.om.util.CommonUtils.callStackToString(CommonUti ls.java:80) DEBUG_FRAME = org.apache.axiom.om.impl.util.OMSerializerUtil.getNextNSPrefix(O MSerializerUtil.java:682) DEBUG_FRAME = org.apache.axiom.om.impl.llom.OMElementImpl.declareNamespace(OME lementImpl.java:372) DEBUG_FRAME = com.ibm.wsspi.sca.jaxws.data.JaxWsNativeDataHolder.constructBody FromBytes(JaxWsNativeDataHolder.java:251) ... [1/24/11 12:11:16:625 PST] 0000007e OMSerializerU 1 org.apache.axiom.om.impl.util.OMSerializerUtil getNextNSPrefix Obtained next prefix:axis2ns2 These messages would appear in trace enabled for org.apache.axiom.*=all
Problem conclusion
The JAX-WS runtime was changed to reuse existing prefixes previously created for the same namespace URI. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.19. 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
PM36257
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
2011-04-04
Closed date
2011-05-20
Last modified date
2011-05-20
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
Document Information
Modified date:
27 October 2021