PI65412: Transaction service may fail to log data correctly when its logs are stored in a database and connection failure occurs

Fixes are available

APAR status

Closed as program error.

Error description

The transaction service failed to write data correctly to
its logs when it failed to connect to the database.  When
the
application server was restarted the transaction service
failed to recover resulting in message WTRN0045W as per the
example below.

[5/15/15 01:00:00:999 EST] 0000008d RegisteredRes E
WTRN0045W: The transaction service cannot recover resource
0000000000000000000000020001. The exception stack trace
follows:
java.lang.Exception: Invalid Xid/recoveryId in transaction
log
at
com.ibm.tx.jta.impl.JTAXAResourceImpl.(JTAXAResourceImpl.j
ava:193)
at
com.ibm.ws.tx.jta.JTAXAResourceImpl.(JTAXAResourceImpl.jav
a:131)
at
com.ibm.ws.tx.jta.RegisteredResources.reconstruct(Registered
Reso
urces.java:218)
at
com.ibm.tx.jta.impl.TransactionImpl.reconstruct(TransactionI
mpl.
java:747)
at
com.ibm.ws.tx.jta.RecoveryManager.handleTranRecord(RecoveryM
anag
er.java:1015)
at
com.ibm.tx.jta.impl.RecoveryManager.replayTranLog(RecoveryMa
nage
r.java:496)
at
com.ibm.tx.jta.impl.RecoveryManager.run(RecoveryManager.java
:209
8)
at java.lang.Thread.run(Thread.java:784)

Local fix

The simplest way to get the server back up is to delete the
transaction
for the table:

DELETE * FROM  LOM_TRX_SCHEMA.WAS_TRAN_LOGTX_A_CL_M_03
WHERE RU_ID=3846 AND
SERVER_NAME="BPMQVCell\BPMQVNode3\AppClusterMember3"

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server users that *
*                  have configured the transaction service to  *
*                  store its logs in a database.               *
****************************************************************
* PROBLEM DESCRIPTION: The transaction service may fail to log *
*                      data correctly when its logs are stored *
*                      in a database in connection failure     *
*                      cases.                                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In the event that the transaction service failed to obtain a
connection to the database used for storing its logs the error
handling was incorrect.

Problem conclusion

The transaction service was modified to handle the failure
correctly. If a connection to the database cannot be obatined
the transaction service marks the logs as failed. The
transaction service will no longer be available on the
application server. If the transaction service logs have been
configured for high availability the peer recovery process will
be initiated.

The fix for this APAR is currently targeted for inclusion in
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

Comments

APAR Information

APAR number
PI65412
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-07-06
Closed date
2016-07-18
Last modified date
2016-07-18

APAR is sysrouted FROM one or more of the following:

PI38387
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
LIBERTY PROFILE
Fixed component ID
5724J0814

Applicable component levels

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

Document Information

Modified date:
04 May 2022

Tips

PI65412: Transaction service may fail to log data correctly when its logs are stored in a database and connection failure occurs

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

R850 PSY

Document Information

Share your feedback

Need support?