PM47486: A SUSPENDED GLOBAL TRANSACTION IS NEVER RESUMED AFTER AN EXCEPTION IS THROWN, THUS EXHAUSTING THE DATA SOURCE POOL

Fixes are available

APAR status

Closed as program error.

Error description

Due to an exception thrown from the transaction extension helper
when a global transaction is to be suspended, it is possible
that the global transaction stays suspended and is never
resumed. This causes connections to remain in connection pools
that are associated with this suspended transaction. This
ultimately causes connection pool exhaustion and hanging threads
when connections are attempted to be retrieved from the, now
exhausted, connection pool.

A connection pool trace will indicate connections are in the
following state...

Connection marked to be destroyed.  Waiting for transaction end
and connection close -
com.ibm.ws.Transaction.JTA.TransactionImpl@2c2c2c2c#tid=70429
MCWrapper id 20882088  Managed connection
WSRdbManagedConnectionImpl@36333633
State:STATE_TRAN_WRAPPER_INUSE Thread Id: 00000343 Thread Name:
Default: 30 Handle count 1 Start time inuse Tue Aug 23 15:56:17
BST 2011 Time inuse 788 (seconds)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: Global transaction is not resumed       *
*                      after scheduler service attempts to     *
*                      start a new local transaction fails     *
*                      with an exception.                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When an application invokes a scheduler service with in a global
transaction context, it will get suspended as the scheduler
attempts to start a new local transaction for its own execution.
At times when the scheduler's attempt to start a new local
transaction fails, the global transaction is never resumed. This
behavior leads to numerous issues such as connection leakage,
application hung etc..

Problem conclusion

The code has been fixed to resume the global transaction, if
any, as a cleanup process.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.43, 7.0.0.23 and 8.0.0.3.  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
PM47486
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-09-09
Closed date
2011-10-24
Last modified date
2011-10-24

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
R800 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":"610","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM47486: A SUSPENDED GLOBAL TRANSACTION IS NEVER RESUMED AFTER AN EXCEPTION IS THROWN, THUS EXHAUSTING THE DATA SOURCE POOL

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?