IBM Support

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

Fixes are available

9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
16.0.0.3: WebSphere Application Server Liberty 16.0.0.3
16.0.0.4: WebSphere Application Server Liberty 16.0.0.4
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
17.0.0.1: WebSphere Application Server Liberty 17.0.0.1
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9

Subscribe

You can track all active APARs for this component.

 

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

  • R850 PSY

       UP

  • R900 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:
03 December 2021