IBM Support

PI73138: TRANSACTION RECOVERY MAY FAIL WHEN A RESOURCE ADAPTER IS EMBEDDED IN AN INSTALLED APPLICATION

Fixes are available

9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
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

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a resource adapter is embedded in an application, when
    the transaction manager tries to recover a transaction
    involving the resource, recovery fails with a classloader
    issue. If the resource adapter is defined at cell/node scope,
    then recovery completes without any issue.
    
    Below is an example callstack generated when attempting to
    recover a WebSphere Adapter for Email embedded in an
    application:
    
    java.lang.NoSuchMethodException:
    com.sun.mail.imap.IMAPStore.<init>(javax.mail.Session,
    javax.mail.URLName)
    at java.lang.Class.throwNoSuchMethodException(Class.java:420)
    at java.lang.Class.getConstructor(Class.java:473)
    at javax.mail.Session.getService(Session.java:782)
    at javax.mail.Session.getStore(Session.java:574)
    at javax.mail.Session.getStore(Session.java:536)
    at javax.mail.Session.getStore(Session.java:515)
    at
    com.ibm.j2ca.email.util.EmailManager.<init>(EmailManager.java:17
    6)
    at
    com.ibm.j2ca.email.EmailEventStore.<init>(EmailEventStore.java:1
    17)
    at
    com.ibm.j2ca.email.EmailResourceAdapter.createEventStore(EmailRe
    sourceAdapter.java:175)
    at
    com.ibm.j2ca.extension.eventmanagement.internal.EventStoreBacked
    XAResource.createEventStoreForRecovery(EventStoreBackedXAResourc
    e.java:112)
    at
    com.ibm.j2ca.extension.eventmanagement.internal.EventStoreBacked
    XAResource.recover(EventStoreBackedXAResource.java:436)
    at
    com.ibm.ws.Transaction.JTA.XARminst.recover(XARminst.java:141)
    at
    com.ibm.ws.Transaction.JTA.XARecoveryData.recover(XARecoveryData
    .java:719)
    at
    com.ibm.tx.jta.impl.PartnerLogTable.recover(PartnerLogTable.java
    :432)
    at
    com.ibm.tx.jta.impl.RecoveryManager.resync(RecoveryManager.java:
    1543)
    at
    com.ibm.tx.jta.impl.RecoveryManager.performResync(RecoveryManage
    r.java:2276)
    at
    com.ibm.ws.tx.jta.RecoveryManager.performResync(RecoveryManager.
    java:119)
    at
    com.ibm.tx.jta.impl.RecoveryManager.run(RecoveryManager.java:222
    9)
    at java.lang.Thread.run(Thread.java:790)
    

Local fix

  • Define the resource at cell/node scope.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Application Server users of       *
    *                  embedded resource adapters                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Transaction recovery fails with         *
    *                      classloading issues when attempting     *
    *                      to recover a resource adapter embedded  *
    *                      in an application.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If an embedded resource adapter loads classes using the
    thread's context class loader, and the classes it loads exist
    both in the application server's runtime and the application
    or resource adapter then the classloader set as the recovery
    thread's context class loader may lead to class loading issues
    causing recovery of the resource to fail.
    

Problem conclusion

  • Typically this can be resolved by selecting the option to
    isolate the resource adapter.
    
    If isolating the resource adapter is not an option when
    recovering a non-isolated, embedded J2C resource adapter then
    the application server's recovery component can be configured
    to set the thread's context class loader to the classloader of
    the resource adapter's XAResource.
    
    To enable the use of the alternate classloader the JVM system
    property below can be specified with a value of true
    
    com.ibm.ws.Transaction.JTA.XARecoveryData.useEmbeddedRAClassLoad
    er
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.13 and 9.0.0.6.  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

    PI73138

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-12-02

  • Closed date

    2017-09-19

  • Last modified date

    2017-09-19

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 May 2022