IBM Support

PM08291: THIS APAR TO PROVIDE A METHOD OF REMOVING RECOVERY LOG ENTRIES FROM THE TRANSACTION SERVICE PARTNER LOGS.

Fixes are available

6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
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
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
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
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
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
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
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
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
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

  • We currently have no method of allowing for the transaction
    service recovery log entries for the resources throwing the
    
    ClassCastException cannot be recovered, and will remain in the
    recovery partner log.
    
    ====> From log files we are seeing following exception:
    
    [2/20/10 0:53:19:583 CET] 00000021 XARecoveryDat <  getXARminst
    Exit
    
    javax.transaction.xa.XAException
     at
    com.ibm.ws.Transaction.JTA.XARecoveryData.getXARminst(XARecovery
    Data.jav
    a:567)
     at
    com.ibm.ws.Transaction.JTA.XARecoveryData.recover(XARecoveryData
    .java:64
    4)
     at
    com.ibm.ws.Transaction.JTA.PartnerLogTable.recover(PartnerLogTab
    le.java:
    524)
     at
    com.ibm.ws.Transaction.JTA.RecoveryManager.resync(RecoveryManage
    r.java:1
    859)
     at
    com.ibm.ws.Transaction.JTA.RecoveryManager.run(RecoveryManager.j
    ava:2580
    )
     at java.lang.Thread.run(Thread.java:810)
    Caused by:
    com.ibm.ws.Transaction.XAResourceNotAvailableException:
    java.lang.ClassCastException:
    com.ibm.j2ca.sap.SAPActivationSpecWithXid
    incompatible with
    com.ibm.j2ca.sap.aep.inbound.SAPAEPActivationSpecWithXid
     at
    com.ibm.ws.Transaction.JTA.ASXAResourceFactoryImpl.getXAResource
    (ASXARes
    ourceFactoryImpl.java:118)
     at
    com.ibm.ws.Transaction.JTA.XARecoveryData.getXARminst(XARecovery
    Data.jav
    a:529)
     ... 5 more
    Caused by: java.lang.ClassCastException:
    com.ibm.j2ca.sap.SAPActivationSpecWithXid incompatible with
    com.ibm.j2ca.sap.aep.inbound.SAPAEPActivationSpecWithXid
     at
    com.ibm.j2ca.sap.SAPResourceAdapter.createEventStore(SAPResource
    Adapter.
    java:122)
     at
    com.ibm.j2ca.base.WBIResourceAdapter.getXAResourcesForAssuredEve
    ntDelive
    ry(WBIResourceAdapter.java:657)
     at
    com.ibm.j2ca.base.WBIResourceAdapter.getXAResources(WBIResourceA
    dapter.j
    ava:380)
     at
    com.ibm.ws.Transaction.JTA.ASXAResourceFactoryImpl.getXAResource
    (ASXARes
    ourceFactoryImpl.java:113)
     ... 6 more
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V6.1 and V7.0                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Periodic recovery attempted on          *
    *                      resource entries in the partner log     *
    *                      that can never be recovered.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An entry in a partner log that describes a resource that
    cannot be recovered (for example, a resource that no longer
    exists, or is no longer contactable) will remain in the
    transaction partner log.  The resource is subject to periodic
    attempts at recovery, which will fail, causing exception
    messages to be logged to SystemOut.
    

Problem conclusion

  • Provide a method to allow for the removal of log entries from
    the transaction partner log.
    
    This functionality is controlled by the following transaction
    service custom property :
    
    Name :  REMOVE_PARTNER_LOG_ENTRY
    Value : A comma-delimited set of recovery ID's of the log
    entries to be removed
    
    Examples :
    
    REMOVE_PARTNER_LOG_ENTRY=2
    REMOVE_PARTNER_LOG_ENTRY=4,13,9,7
    
    The recovery ID's of resource entries to be removed are only
    printed out with Transaction tracing enabled - the example
    trace entry following shows a resource having a recovery ID
    value of 4 :
    
    index=7, recoveryID=4, recovered=true, terminating=false,
    loggedToDisk=true, data=com.ibm.ejs.j2c......
    
    
    For each server that is required to have the new behaviour
    enabled :
    
    1. Login to the Administrative Console
    2. Select Servers -> Application Servers -> server ->
    Container Services -> Transaction Service
    3. Select the Configuration tab
    4. Select Custom Properties
    5. Press new
    6. Enter REMOVE_PARTNER_LOG_ENTRY as the name
    7. Enter comma-delimited list of Recovery ID's as the value
    8. Click Ok
    9. Save changes
    10. Restart the server
    
    Once you have configured the transaction service custom
    property you must start the server in recovery only mode
    (server started with the -recovery option) to delete the
    entries from the partner log.  No entries will be deleted if
    there are transactions requiring recovery currently recorded
    in the transaction log.
    
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.33 and 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

    PM08291

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    61W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-02-22

  • Closed date

    2010-05-21

  • Last modified date

    2010-05-25

  • 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

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 6.1

Reference #: PM08291

Modified date: 25 May 2010