PK72183: WHILE PERFORMING SERVER SHUTDOWN, A THREAD WAS REPORTED AS BEING HUNG. THE SERVER WAS PREVENTED FROM STOPPING.

Fixes are available

APAR status

Closed as program error.

Error description

While attempting to shutdown a server, a thread is reported as
being  hung :

Message: BBOO0221W: WSVR0605W: Thread
"WebSphere:ORB.thread.pool t=009c27b8" (00000017) has been
active for 712196 milliseconds and may be hung.  There is/are
1 thread(s) in total in the server that may be hung.
at
com.ibm.ws390.tx.NativeTransactionContext.processTmp(Native
Method)
at com.ibm.ws390.tx.NativeTransactionContext.processTmp
(NativeTransactionContext.java:604)
at
com.ibm.ws390.tx.NativeGlobalTransactionContext.commitOnePhase
(NativeGlobalTransactionContext.java:911)
at com.ibm.ws.tx.jta.TransactionImpl.prepareZOSResources
(TransactionImpl.java:636)
at com.ibm.tx.jta.TransactionImpl.prepareResources
(TransactionImpl.java:1458)
at com.ibm.ws.tx.jta.TransactionImpl.stage1CommitProcessing
(TransactionImpl.java:500)
at com.ibm.tx.jta.TransactionImpl.processCommit
(TransactionImpl.java:978)
at com.ibm.tx.jta.TransactionImpl.commit
(TransactionImpl.java:913)
at com.ibm.ws.tx.jta.TranManagerImpl.commit
(TranManagerImpl.java:369)
at com.ibm.tx.jta.TranManagerSet.commit
(TranManagerSet.java:161)
at com.ibm.ejs.csi.TranStrategy.commit
(TranStrategy.java:915)
at com.ibm.ejs.csi.TranStrategy.postInvoke
(TranStrategy.java:228)
at com.ibm.ejs.csi.RequiresNew.postInvoke
(RequiresNew.java:137)
at com.ibm.ejs.csi.TransactionControlImpl.postInvoke
(TransactionControlImpl.java:561)
at com.ibm.ejs.container.EJSContainer.postInvoke
(EJSContainer.java:4512)

The server cannot be stopped from the Administration Console,
and the running process cannot be terminated.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All Users of IBM WebSphere Application      *
*                  Server V7.0 for z/OS                        *
****************************************************************
* PROBLEM DESCRIPTION: Address a number of transactions        *
*                      problems discovered during extended     *
*                      testing.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
(1) While attempting to shutdown a server, a thread is
reported as being hung :
Message: BBOO0221W: WSVR0605W: Thread
"WebSphere:ORB.thread.pool t=009c27b8" (00000017) has been
active for 712196 milliseconds and may be hung.
There is/are 1 thread(s) in total in the server that may be
hung.
at
com.ibm.ws390.tx.NativeTransactionContext.processTmp(Native
Method)
at com.ibm.ws390.tx.NativeTransactionContext.processTmp
(NativeTransactionContext.java:604)
at
com.ibm.ws390.tx.NativeGlobalTransactionContext.commitOnePhase
(NativeGlobalTransactionContext.java:911)
at com.ibm.ws.tx.jta.TransactionImpl.prepareZOSResources
(TransactionImpl.java:636)
at com.ibm.tx.jta.TransactionImpl.prepareResources
(TransactionImpl.java:1458)
at com.ibm.ws.tx.jta.TransactionImpl.stage1CommitProcessing
(TransactionImpl.java:500)
at com.ibm.tx.jta.TransactionImpl.processCommit
(TransactionImpl.java:978)
at com.ibm.tx.jta.TransactionImpl.commit
(TransactionImpl.java:913)
at com.ibm.ws.tx.jta.TranManagerImpl.commit
(TranManagerImpl.java:369)
...

The server cannot be stopped from the Administrative Console,
and the running process cannot be terminated.

Threads are becoming stuck due to protocol messages being sent
but never responded to by another server involved in the
transaction.  This is related to blocking issues on
high-priority threads.

(2) Incoming Web Services Atomic Transactions were not being
handled in a manner consistent with the settings on the
application deployment descriptor.

(3) IllegalStateException thrown and FFDC logged while
attempting to resume a transaction.
FFDC Exception:java.lang.IllegalStateException
SourceId:com.ibm.ws.Transaction.TranManagerImpl.resume
ProbeId:201 Reporter:com.ibm.ws.tx.jta.TranManagerImpl@789f789f
java.lang.IllegalStateException: Context is not currently
suspended
 at
com.ibm.ws390.tx.NativeTransactionContext.resume(NativeTransacti
onContext.java:264)
 at
com.ibm.ws.tx.jta.TranManagerImpl.resume(TranManagerImpl.java:15
8)
 at
com.ibm.tx.jta.TranManagerSet.resume(TranManagerSet.java:181)
 at
com.ibm.ejs.csi.TransactionControlImpl.resumeGlobalTx(Transactio
nControlImpl.java:1256)
 at
com.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionCon
trolImpl.java:596)
 at
com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:
4549)

Transaction timeout processing caused problem with the resume
and suspend processing of the transaction context.

(4) Heuristic forget retry processing was failing due to the
failing resource being omitted from the list of resources to
retry.

(5) Web Services Atomic Transactions failing with
WebServicesFault caused by
WebServicesFault


 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}MustUnderstand


 faultString: WSWS3173E: Error: Did not understand
"MustUnderstand"
header(s):{http://schemas.xmlsoap.org/ws/2004/10/wscoor}Coordina
tionContext


 faultActor: null


 faultDetail:


WSWS3173E: Error: Did not understand "MustUnderstand"
header(s):{http://schemas.xmlsoap.org/ws/2004/10/wscoor}Coordina
tionContext

Handlers were unable to differentiate multiple contexts for
the same transaction if different Web Services - Transaction
versions were in use.

(6) Various Web Services - Atomic Transactions failures due to
attempting to utilise CoordinationContext before initialisation.

Problem conclusion

(1) Corrected the blocking issues on high-priority threads.

(2) Changed to correctly handle incoming Web Services Atomic
Transaction contexts as defined by the application deployment
descriptor.

(3) Corrected processing of transaction contexts on timeout
threads.

(4) Changed to ensure that failed resource was correctly added
to list of resources to retry.

(5) Changed to handle multiple contexts for the same
transaction based on the Web Services - Transaction version.

(6) Initialise CoordinationContext earlier during Web Services
- Atomic Transaction processing.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.1.  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
PK72183
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-16
Closed date
2008-11-17
Last modified date
2008-11-17

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

R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022

Tips

PK72183: WHILE PERFORMING SERVER SHUTDOWN, A THREAD WAS REPORTED AS BEING HUNG. THE SERVER WAS PREVENTED FROM STOPPING.

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

R700 PSY

Document Information

Share your feedback

Need support?