IBM Support

PM07874: XA RECOVERY SERVICEABILITY DEFICIENCY

Fixes are available

7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 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

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • Currently, information required for post-mortem troubleshooting
    of certain types of WebSphere Application Server XA recovery
    issues -- for example, unresolved indoubt transaction branches
    remaining after WebSphere Application Server recovery -- is
    either logged only at an excessively verbose (and therefore
    impractical) trace level, or potentially not logged at all.
    
    To assist with post-mortem troubleshooting of recovery issues --
    whether caused by WebSphere Application Server (WAS) or
    downstream participants WebSphere Application Server should
    report recovery-related information either via a much more
    granular trace level (AUDIT has been mentioned), or in some
    cases directly to SystemOut if/as appropriate.
    
    In each case, a preferred log/trace level as input for your
    consideration:
    
    (1) AUDIT: Recovery CRUUID and epoch -- as distinct values.
    (2) INFO:  Transactions to be recovered/committed, as per the
    tranlogs.
    (3) AUDIT: All branches reported by participants that were
    initiated by the Transaction Manager (TM) being recovered,
    whether for the current or a past cruuid/epoch.
    (4) WARN:  Branches reported "late" by the RM, that is, from a
    prior epoch.
    (5) AUDIT: Branch outcomes delivered to each RM, including RM
    response.
    (6) WARN:  Branches reporting heuristic completion conflicting
    w/ WAS.
    (7) INFO:  Branches reporting heuristic completion consistent
    w/ WAS.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Add extra informational messages to     *
    *                      report on Transaction Service           *
    *                      recovery progress.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Currently, information required for troubleshooting of certain
    types of WebSphere Application Server XA recovery issues (for
    example, unresolved indoubt transaction branches remaining
    after WebSphere Application Server recovery) is logged only at
    trace level.
    
    To assist with troubleshooting of recovery issues (whether
    caused by WebSphere Application Server or downstream
    participants) WebSphere Application Server should report
    recovery-related information.
    

Problem conclusion

  • The Transaction Service has been changed to produce additional
    console messages during recovery.
    
    If you wish to suppress the new logging messages there is a
    Transaction Service custom property that you can set to
    disable the messages:
    
    1. Login to the Administrative Console
    2. Select Servers -> WebSphere Application Servers -> server
    -> Container Services -> Transaction Service
    3. Select the Configuration tab
    4. Select Custom Properties
    5. Press new
    6. Enter DISABLE_RECOVERY_AUDIT_LOGGING as the name, and true
    as the value
    7. Click Ok
    8. Save changes
    9. Restart the server
    
    Additional information for z/OS Users:
    By default, the messages will not be displayed when running
    WebSphere Application Server on z/OS, in order to reduce the
    large number of messages that may be produced on z/OS.
    To enable the new logging messages you will need to define the
    custom property as described previously and set the value to
    false.
    
    The new message are (see the Information Center for
    explanations):
    
    WTRN0132I:
    Transaction recovery for {0} initiated with server uuid {1}
    and restart epoch {2}
    
    WTRN0133I:
    Transaction recovery processing for this server is complete
    
    WTRN0134I:
    Recovering {0} XA resource manager(s) from the transaction
    partner logs
    
    WTRN0135I:
    Transaction service recovering no transactions.
    
    WTRN0136I:
    Processing recovered transaction {0} (tid={1}) with {2}
    
    WTRN0137I:
    Recovered transaction (tid={0}) committing xid {1} with {2}
    
    WTRN0138I:
    Recovered transaction (tid={0}) rolling back xid {1} with {2}
    
    WTRN0139I:
    Recovered transaction (tid={0}) forgetting xid {1} with {2}
    
    WTRN0140I:
    Recovered transaction (tid={0}) committed xid {1} successfully
    with {2}
    
    WTRN0141I:
    Recovered transaction (tid={0}) commit of xid {1} with {2}
    resulted in {3}
    
    WTRN0142I:
    Recovered transaction (tid={0}) rolled back xid {1}
    successfully with {2}
    
    WTRN0143I:
    Recovered transaction (tid={0}) rollback of xid {1} with {2}
    resulted in {3}
    
    WTRN0144I:
    Recovered transaction (tid={0}) forgot xid {1} successfully
    with {2}
    
    WTRN0145I:
    Recovered transaction (tid={0}) forget of xid {1} with {2}
    resulted in {3}
    
    WTRN0146I:
    Obtained {0} xid(s) from xa recover on {1} of which {2} will
    be processed by this server
    
    WTRN0147W:
    Recovered xid {0} from {1} is from a earlier restarted server
    instance with epoch {2}
    
    WTRN0148I:
    Recovered xid {0} from {1} - xid has no associated transaction
    and will be rolled back
    
    WTRN0149I:
    Recovered xid {0} from {1} - xid has associated transaction
    (tid={2}) with logged state {3}
    
    WTRN0150I:
    Response from rolling back recovered xid {0} from {1} - {2}
    
    WTRN0151I:
    Preparing to call xa recover on {0}
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.13.  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

    PM07874

  • 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

    2010-02-18

  • Closed date

    2010-06-10

  • Last modified date

    2010-06-10

  • 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

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM07874

Modified date: 10 June 2010