IBM Support

PI12449: SERVER FAILS TO START DUE TO TRANSACTION RECOVERY FAILURE

Fixes are available

8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
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
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
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
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

Subscribe

You can track all active APARs for this component.

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                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Server fails to start due to            *
    *                      transaction recovery attempting to      *
    *                      recover a resource that is no longer    *
    *                      present in recovery log.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A partner entry in the XA recovery log entry describing a
    remote subordinate server was marked as recovered in error,
    and subsequently removed from the log during server shutdown.
    The next server restart attempted to recover a transaction that
    referenced this remote subordinate server, failed to find the
    resource in the partner log, resulting in the server failing
    to start.
    

Problem conclusion

  • Ensure that remote resource references are not flagged as
    recovered by checking for references that refer to the same
    resource but show conflicting recovery status.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.35, 8.0.0.10 and 8.5.5.4.  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

    PI12449

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-02-25

  • Closed date

    2014-06-25

  • Last modified date

    2014-06-25

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

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

    PI19361

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PI12449

Modified date: 25 June 2014