PI19361: APPLICATION SERVER FAILED TO START BECAUSE TRANSACTION RECOVERY FAILED

8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
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.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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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

• WSVR0009E  org.omg.CORBA.INV_OBJREF error that occurs
  periodically during appserver startup. The information recorded
  in the transaction  and partner logs have become disassociated.
   This has resulted in  transactions recorded in the tranlog
  attempting to contact resources  that are no longer present in
  the partner logs, leading to the exception  as shown in example
  here :
  
  E [11/21/13 08:50:56:997] 0000000e RegisteredRes [WTRN0045W:
  The  transaction service cannot recover resource
  000000000000000a. The exception stack trace follows:
  org.omg.CORBA.INV_OBJREF:   vmcid: 0x0  minor code: 0
  completed: No]
  at
  com.ibm.ws.Transaction.JTS.WSCoordinatorWrapper.<init>(WSCoordin
  atorWrap per.java:163)
  at
  com.ibm.ws.tx.jta.RegisteredResources.reconstruct(RegisteredReso
  urces.ja va:246)
  at
  com.ibm.tx.jta.TransactionImpl.reconstruct(TransactionImpl.java:
  704)
  at
  com.ibm.ws.tx.jta.RecoveryManager.handleTranRecord(RecoveryManag
  er.java:
  1076)
  at
  com.ibm.tx.jta.RecoveryManager.replayTranLog(RecoveryManager.jav
  a:490)
  at
  com.ibm.tx.jta.RecoveryManager.run(RecoveryManager.java:2087)
  at java.lang.Thread.run(Thread.java:738)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile - WebSphere MQ       *
  *                  messaging provider                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: Application Server will fail to start   *
  *                      due to attempts to recover resources no *
  *                      longer present in the transaction       *
  *                      logs.                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An unrecovered resource stays logged in the XA partner log, and
  attempts to recover the resource will continue after each server
  restart.  If the same resource is enlisted with a new
  transaction subsequent to the server restart, a new logged
  record is recorded in the partner log for the resource. If this
  reference subsequently requires recovery, then the partner log
  will have two references to that resource.  During server
  shutdown, those resources that are still unrecovered are merged
  into the XA partner log with the currently active resources.
  Due to the way the resource matching occurred on some resources,
  only the first resource reference was ever located and logged
  during the merge process, causing the server to fail on the next
  restart due to a missing resource reference.
  

Problem conclusion

• Corrected the merging process that occurs during server shutdown
  to ensure that all resources requiring recovery are correctly
  logged.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.5.  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 is sysrouted FROM one or more of the following:

  PI12449

• 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