PI88168: WEBSPHERE APPSERVER STARTUP FAILS WITH WTRN0045W ERRORS

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
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 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
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
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
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• Websphere Application Server configured to store
  transaction service logs in a relational database fails
  on startup with the following error in the SystemOut.log:
  
  WTRN0045W: The transaction service cannot recover resource
  00000000000000000000000a0002. 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:497)
  at
  com.ibm.tx.jta.impl.RecoveryManager.run(RecoveryManager.java:210
  8)
  at java.lang.Thread.run(Thread.java:801)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server users of a     *
  *                  relational database to store the            *
  *                  transaction service logs.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Server startup fails with message       *
  *                      WTRN0045W reporting Invalid             *
  *                      Xid/recoveryId in transaction log       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The transaction service writes state to persistent storage so
  that the ACID properties of transactions can be maintained in
  the event of application server failure.  Only state changes
  that are required for such transactional recovery are forced
  to the logs.  Other changes, which includes deletion of the
  transactions and transaction partners, are unforced and such
  changes are persisted the next time a forced write is required.
  When writing data to transaction service logs stored in a
  relational database SQL batch processing is used when
  processing both the unforced writes and the forced write.
  This performs the required record creations, then record
  updates, then record deletions. Records are indexed by a
  unique identifier.
  When a transaction partner is recovered on restart it is
  deleted from the partner log but the deletion is unforced. The
  unique identifier used within the recovery log may be
  reallocated to a new recovery log record for a new transaction
  partner.  If this new partner record is written before the old
  partner record's unforced deletion was persisted then this
  results in the new record being created and then erroneously
  deleted.
  This error will be undetected until transaction recovery
  occurs during an application server restart that follows an
  unclean application server shutdown, normally the result of a
  sudden application server failure.  In such a circumstance, if
  transaction recovery processes a transaction that references
  the deleted partner the error indicated by the WTRN0045 occurs.
  

Problem conclusion

• The recovery log service was modified so that the unique
  identifiers obtained from recoverable units read during
  recovery processing are not reallocated during the lifetime of
  the current execution of the application server.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.5.5.14 and 9.0.0.8.  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:

• 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

• R850 PSY

     UP

• R900 PSY

     UP