IBM Support

PM06697: XAEXCEPTION ERROR CODE:XAER_NOTA DURING XA RECOVERY IF TWO INSTANCES OF THE ADAPTER INSTALLED ON THE APPSERVER

Fixes are available

7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
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 program error.

Error description

  • Using a JCA 1.5 compliant Resource Adapter (RA) that has two
    instances installed.  During the XA recovery of in-doubt
    transactions, the recovery succeeds on the first instance of the
    adapter but not on the second instance unless the -recovery flag
    is set on the AppServer.
    This problem occurs on WebSphere Application Server V7.0 but
    not on WebSphere Application Server V6.1.
    .
    The problem would happen during XA recovery, which is done
    during the start processing of the Application Server.  The
    SystemOut.log would log and FFDC message.
    [1/4/10 15:08:29:337 EST] 00000007 FfdcProvider  I
    com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC
    Incident emitted on
    C:Program
    FilesIBMWebSphereAppServerprofilesAppSrv01logsffdcserver
    1_65c665c6_10.01.04_15.08.28.7597095033213021147076.txt
    com.ibm.ws.Transaction.JTA.JTAXAResourceImpl.commit 317
    .
    [1/4/10 15:08:29:431 EST] 00000007 FfdcProvider  I
    com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC
    Incident emitted on
    C:Program
    FilesIBMWebSphereAppServerprofilesAppSrv01logsffdcserver
    1_65c665c6_10.01.04_15.08.29.36826779930054213541.txt
    com.ibm.tx.jta.RegisteredResources.deliverOutcome 1923
    .
    The exception text in the FFDC file that is stored is
    [1/4/10 15:08:28:884 EST]     FFDC
    
    Exception:javax.transaction.xa.XAException
    SourceId:com.ibm.ws.Transaction.JTA.JTAXAResourceImpl.commit
    ProbeId:317
    Reporter:com.ibm.ws.tx.jta.JTAXAResourceImpl@73017301
    javax.transaction.xa.XAException
    at com.ibm.dtp.connector.DtpXAResource.commit
    (DtpXAResource.java:291)
    at com.ibm.tx.jta.JTAXAResourceImpl.commit
    (JTAXAResourceImpl.java:295)
    at com.ibm.tx.jta.RegisteredResources.deliverOutcome
    (RegisteredResources.java:1570)
    at com.ibm.tx.jta.RegisteredResources.distributeOutcome
    (RegisteredResources.java:1908)
    at com.ibm.tx.jta.RegisteredResources.distributeCommit
    (RegisteredResources.java:2216)
    at com.ibm.tx.jta.TransactionImpl.recoverCommit
    (TransactionImpl.java:2007)
    at com.ibm.tx.jta.TransactionImpl.recover
    (TransactionImpl.java:852)
    at com.ibm.ws.tx.jta.TransactionImpl.recover
    (TransactionImpl.java:2320)
    at com.ibm.tx.jta.RecoveryManager.resync
    (RecoveryManager.java:1539)
    at com.ibm.ws.tx.jta.RecoveryManager.performResync
    (RecoveryManager.java:126)
    at
    com.ibm.tx.jta.RecoveryManager.run(RecoveryManager.java:2200)
    

Local fix

  • Set -recovery option on the Application Server and restart it.\
    See the Information Center page entitled
    Restarting an application server in recovery mode
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: XAException on recovery thread during   *
    *                      server starup.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    There can exist multiple Resource Adapters (RA) with the same
    bean class name in the configuration. Currently, the code does
    not account for this scenario and it searches for RA instances
    by classname. Therefore, only one RA instance is returned for
    recovery.
    

Problem conclusion

  • The code is changed such that it is now aware of the fact that
    the classname may not be unique in the configuration. It,
    rather, uses a unique id, raKey, while searching for RA
    instances from the RA list.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.11.  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

    PM06697

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-02-03

  • Closed date

    2010-03-24

  • Last modified date

    2010-03-24

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021