PI65127: DEADLOCK ISSUE WHEN TRANSACTION SERVICE LOGS STORED IN A DATABASE AND TRANSACTIONAL HIGH AVAILABILITY IS CONFIGURED

Fixes are available

APAR status

Closed as program error.

Error description

When the server is stopping, the server received
SQLException(SQLCODE -911) from tranlog db side.


* Exception Stack *
com.ibm.db2.jcc.am.SqlTransactionRollbackException: Error for
batch element #1: The current transaction was rolled back
because of error "-911".
Associated tokens: "" SQLCODE=-1476,
SQLSTATE=40506,DRIVER=4.19.26

at com.ibm.db2.jcc.am.kd.a(Unknown Source)
:
at com.ibm.db2.jcc.t4.j.c(Unknown Source)
at com.ibm.db2.jcc.am.gp.executeBatch(Unknown Source)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteBatc
h(WSJdbcPreparedStatement.java:1037)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.executeBatch(WSJdbcSta
tement.java:843)
at
com.ibm.ws.recoverylog.custom.jdbc.impl.SQLMultiScopeRecoveryLog
.executeBatchStatements(SQLMultiScopeRecoveryLog.java:2337)
at
com.ibm.ws.recoverylog.custom.jdbc.impl.SQLMultiScopeRecoveryLog
.internalForceSections(SQLMultiScopeRecoveryLog.java:2050)
at
com.ibm.ws.recoverylog.custom.jdbc.impl.SQLMultiScopeRecoveryLog
.internalKeypoint(SQLMultiScopeRecoveryLog.java:1855)
at
com.ibm.ws.recoverylog.custom.jdbc.impl.SQLMultiScopeRecoveryLog
.closeLog(SQLMultiScopeRecoveryLog.java:1404)
at
com.ibm.tx.jta.impl.RecoveryManager.postShutdown(RecoveryManager
.java:799)
at
com.ibm.ws.tx.jta.FailureScopeController.shutdown(FailureScopeCo
ntroller.java:344)
at
com.ibm.ws.runtime.component.TxServiceImpl.destroy(TxServiceImpl
.java:1207)
at
com.ibm.ws.runtime.component.ContainerHelper.destroyComponent(Co
ntainerHelper.java:340)
:
at
com.ibm.ws.runtime.component.ServerCollaborator$StopAction.alarm
(ServerCollaborator.java:831)
:
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1864)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server users that     *
*                  have                                        *
*                  configured the transaction service to store *
*                  its logs in a database.                     *
****************************************************************
* PROBLEM DESCRIPTION: SQLException(SQLCODE -911) occurs while *
*                      processing the transaction service      *
*                      logs.                                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When storing recovery logs for the transaction or compensation
services in a relational database, the recovery log service
implements a locking algorithm to ensure that only one
application server can take ownership of and access a particular
log.  This is required when 'transactional high availability' is
configured since the HA framework cannot guarantee that at one
point in time only a single application server will be
instructed to process a log.  This algorithm was defective
resulting in a deadlock between one application server deleting
records on shutdown and a peer application server concurrently
attempting recovery on the same logs.

Problem conclusion

The locking algorithm was fixed.

The fix for this APAR is currently targeted for inclusion in
WebSphere Application Server fix packs 8.0.0.13, 8.5.5.11 and
9.0.0.1 and WebSphere Application Server Liberty fix pack
16.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

Transactional High Availability could be either disabled or
configured to use manual peer recovery.

Comments

APAR Information

APAR number
PI65127
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-06-29
Closed date
2016-09-13
Last modified date
2016-09-13

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

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

Document Information

Modified date:
04 May 2022

Tips

PI65127: DEADLOCK ISSUE WHEN TRANSACTION SERVICE LOGS STORED IN A DATABASE AND TRANSACTIONAL HIGH AVAILABILITY IS CONFIGURED

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

R800 PSY

Document Information

Share your feedback

Need support?