PM06800: THREAD DEADLOCK MAY OCCUR ON "FINALIZER" THREAD WHEN A JAX-RPC APPLICATION IS INVOKED AFTER PK84543

Fixes are available

APAR status

Closed as program error.

Error description

While invoking a JAX-RPC application, a thread deadlock
may occur.

Here is an example from the javacore of the deadlocked
threads.

JAVA CORE:
==========

Thread "Finalizer" (0x74547CA8)
which is waiting for:
sys_mon_t:0x7BF53538 infl_mon_t: 0x00000000:
java.lang.String@376091B8/376091C0:
which is owned by:
Thread "WebContainer : XX" (0x82090E28)

Here is the location of the Finalizer thread from the javacore.

Finalizer" (TID:0x300CE0B0, sys_thread_t:0x74547CA8, state:MW,
native
ID:0x304) prio=8
com.ibm.ws.webservices.engine.handlers.jaxrpc.PoolManagerProxy$P
oolProxy
.destroy(PoolManagerProxy.java(Compiled Code))
com.ibm.ws.webservices.engine.handlers.jaxrpc.WASHandlerPool.des
troy(WAS
HandlerPool.java(Compiled Code))
com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandlerChain
.remove(
JAXRPCHandlerChain.java(Compiled Code))
java.util.AbstractList$Itr.remove(AbstractList.java(Compiled
Code))

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server users of   *
*                  JAX-RPC                                     *
****************************************************************
* PROBLEM DESCRIPTION: A thread deadlock may occur while       *
*                      running a JAX-RPC application           *
*                      containing JAX-RPC handlers             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a JAX-RPC application is invoked, a thread deadlock
may occur.

Here is an example from the javacore of the deadlocked
threads.

JAVA CORE:
==========

Thread "Finalizer" (0x74547CA8)
which is waiting for:
sys_mon_t:0x7BF53538 infl_mon_t: 0x00000000:
java.lang.String@376091B8/376091C0:
which is owned by:
Thread "WebContainer : XX" (0x82090E28)


Here is the location of the Finalizer thread from the javacore.

Finalizer" (TID:0x300CE0B0, sys_thread_t:0x74547CA8, state:MW,
native
ID:0x304) prio=8
com.ibm.ws.webservices.engine.handlers.jaxrpc.PoolManagerProxy$P
oolProxy
.destroy(PoolManagerProxy.java(Compiled Code))
com.ibm.ws.webservices.engine.handlers.jaxrpc.WASHandlerPool.des
troy(WAS
HandlerPool.java(Compiled Code))
com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandlerChain
.remove(
JAXRPCHandlerChain.java(Compiled Code))
java.util.AbstractList$Itr.remove(AbstractList.java(Compiled
Code))

This problem will only occur if the WebSphere Application
Server includes the PK84543 fix that was shipped with fixpacks
6.0.2.37, 6.1.0.27, and 7.0.0.5.  In addition, the customer
must be using JAX-RPC handlers.

The problem is frequently seen if the trace logging is
requested.

Problem conclusion

APAR PK84543 contained a segment of code that attempted to
obtain a lock that might already be in use by another thread.
This caused a "deadlock" condition.  Neither thread could
proceed.

This segment of code has been removed.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.41, 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
PM06800
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
60A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-04
Closed date
2010-02-26
Last modified date
2010-02-26

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

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

PM06800: THREAD DEADLOCK MAY OCCUR ON "FINALIZER" THREAD WHEN A JAX-RPC APPLICATION IS INVOKED AFTER PK84543

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?