PI38387: WHEN STORING TRANSACTION SERVICE LOGS IN A NON-HA DATABASE DATA MAY BE LOST AND THE TRANSACTION SERVICE MAY FAIL TO

8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

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.<init>(JTAXAResourceImpl.j
  ava:193)
  at
  com.ibm.ws.tx.jta.JTAXAResourceImpl.<init>(JTAXAResourceImpl.jav
  a:131)
  at
  com.ibm.ws.tx.jta.RegisteredResources.reconstruct(RegisteredReso
  urces.java:218)
  at
  com.ibm.tx.jta.impl.TransactionImpl.reconstruct(TransactionImpl.
  java:747)
  at
  com.ibm.ws.tx.jta.RecoveryManager.handleTranRecord(RecoveryManag
  er.java:1015)
  at
  com.ibm.tx.jta.impl.RecoveryManager.replayTranLog(RecoveryManage
  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:  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 availbility the peer recovery process
  will be initiated.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.11 and 8.5.5.7.  Please refer to the
  Recommended Updatespage for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

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

  PI65412

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY

     UP

• R850 PSY

     UP