PK71392: SYNCHRONIZATION LOCK CONTENTION CAUSES WEBSERVICES SLOW PERFORMANCE ON WEBSERVICES CALLS.

Fixes are available

APAR status

Closed as program error.

Error description

WebServices calls are forced to wait to for a synchronization
lock to complete a WebServices call. A web services engine
synchronization issue is causing waits for
com.ibm.ws.webservices.engine.client.Call.getWSDLQuery(Call.java
:2306)

A sample thread dump shows this sort of java stack in the Web
Container thread pool threads.  The synchronization lock that is
the bottleneck is this
com.ibm.ws.webservices.engine.client.Call.getWSDLQuery(Call.java
:2306)
- waiting to lock <0xb2de2258> (a com.ibm.wsdl.DefinitionImpl)
at
com.ibm.ws.webservices.engine.client.Call.getWSDLQueryOperationD
esc(Call.java:2409)
.----------------------------------------------------------
Here is a fuller java stack dump showing the lock wait.
"Default : 25" daemon prio=5 tid=0x03b00578 nid=0x12e waiting
for monitor entry [0x6a07c000..0x6a07fc28]
at
com.ibm.ws.webservices.engine.client.Call.getWSDLQuery(Call.java
:2306)
- waiting to lock <0xb2de2258> (a com.ibm.wsdl.DefinitionImpl)
at
com.ibm.ws.webservices.engine.client.Call.getWSDLQueryOperationD
esc(Call.java:2409)
at
com.ibm.ws.webservices.engine.client.Call.loadOperationFromWSDL(
Call.java:2448)
at
com.ibm.ws.webservices.engine.client.Call.invoke(Call.java:1505)
at
com.ibm.ws.webservices.multiprotocol.AgnosticCall.invoke(Agnosti
cCall.java:171)
at
com.ibm.ws.sca.internal.webservice.handler.PortHandler$Operation
Handler.invoke(PortHandler.java:192)
.--------------------------
"Default : 20" daemon prio=5 tid=0x03446688 nid=0x11f waiting
for monitor entry [0x5ea7b000..0x5ea7fc28]
at
com.ibm.ws.webservices.engine.client.Call.getWSDLQuery(Call.java
:2306)
- waiting to lock <0xb2de2258> (a com.ibm.wsdl.DefinitionImpl)
at
com.ibm.ws.webservices.engine.client.Call.getWSDLQueryOperationD
esc(Call.java:2409)
at
com.ibm.ws.webservices.engine.client.Call.loadOperationFromWSDL(
Call.java:2448)
at
com.ibm.ws.webservices.engine.client.Call.setOperation(Call.java
:1373)
at
com.ibm.ws.webservices.engine.client.Service.createCall(Service.
java:990)
at
com.ibm.ws.webservices.multiprotocol.AgnosticCall.createCall(Agn
osticCall.java:453)
at
com.ibm.ws.webservices.multiprotocol.AgnosticCall.getProtocolSpe
cificCall(AgnosticCall.java:360)
at
com.ibm.ws.webservices.multiprotocol.AgnosticCall.invoke(Agnosti
cCall.java:146)
at
com.ibm.ws.sca.internal.webservice.handler.PortHandler$Operation
Handler.invoke(PortHandler.java:192)
.--------------------------------------
This is the thread that holds the lock. It holds it for the
time it parses the wsdl document.  It could release the lock
sooner.
"Default : 7" daemon prio=5 tid=0x04431268 nid=0xfc runnable
[0x60b7a000..0x60b7fc28]
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
- locked <0x9c8e9268> (a sun.misc.Launcher$ExtClassLoader)
at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
- locked <0x9c8e9220> (a sun.misc.Launcher$AppClassLoader)
at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
- locked <0x9c8e9220> (a sun.misc.Launcher$AppClassLoader)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.net.URL.getURLStreamHandler(URL.java:1047)
at java.net.URL.<init>(URL.java:542)
at java.net.URL.<init>(URL.java:434)
at java.net.URL.<init>(URL.java:383)
at
com.ibm.ws.webservices.engine.utils.JavaUtils.makePackageName(Ja
vaUtils.java:1057)
at
com.ibm.ws.webservices.engine.utils.Namespaces.getCreate(Namespa
ces.java:141)
at
com.ibm.ws.webservices.wsdl.symbolTable.SymbolTable.collectNames
paces(SymbolTable.java:4249)
at
com.ibm.ws.webservices.wsdl.symbolTable.SymbolTable.firstPass(Sy
mbolTable.java:958)
at
com.ibm.ws.webservices.wsdl.symbolTable.SymbolTable.populateUsin
gDefinition(SymbolTable.java:941)
at com.ibm.ws.webservices.wsdl.Parser.run(Parser.java:408)
at
com.ibm.ws.webservices.wsdl.toJava.Emitter.run(Emitter.java:844)
at
com.ibm.ws.webservices.tools.WSDLQuery.parse(WSDLQuery.java:198)
at
com.ibm.ws.webservices.engine.client.Call$2.run(Call.java:2283)
at java.security.AccessController.doPrivileged(Native Method)
at
com.ibm.ws.webservices.engine.client.Call.invokeWSDLQueryParse(C
all.java:2280)
at
com.ibm.ws.webservices.engine.client.Call.getWSDLQuery(Call.java
:2365)
- locked <0xb2de2258> (a com.ibm.wsdl.DefinitionImpl)
at
com.ibm.ws.webservices.engine.client.Call.getWSDLQueryOperationD
esc(Call.java:2409)
at
com.ibm.ws.webservices.engine.client.Call.loadOperationFromWSDL(
Call.java:2448)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server users of       *
*                  JAX-RPC web services applications           *
****************************************************************
* PROBLEM DESCRIPTION: Synchronization within web services     *
*                      Call.getWSDLQuery method is causing     *
*                      delays.                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A thread dump showed objects waiting on getQWSDLQuery due to a
synchronization lock.

com.ibm.ws.webservices.engine.client.Call.getWSDLQuery(Call.java
:2306)
waiting to lock <0xb2de2258> (a com.ibm.wsdl.DefinitionImpl)  at
com.ibm.ws.webservices.engine.client.Call.getWSDLQueryOperationD
esc(Call.java:2409)

Problem conclusion

The synchronization was evaluated and reduced in size.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.35, 6.1.0.23 and  7.0.0.5.  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
PK71392
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
60W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-02
Closed date
2008-12-19
Last modified date
2008-12-19

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

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
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.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK71392: SYNCHRONIZATION LOCK CONTENTION CAUSES WEBSERVICES SLOW PERFORMANCE ON WEBSERVICES CALLS.

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

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?