IBM Support

PM04318: BBOO0222I: WTRN0108I: ATREINT5 ERROR SEEN IN APPLICATION SERVER,TRANSACTION HANGS AND CANCEL IS NEEDED TO RELEASE THE DB2 LOCKS.

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
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In a WebSphere Application Server using OLA, an EJB makes a call
    to DB2 to update or add information to the database. The
    transaction is of type "required", 2-phase commit.
    
    The transaction appears complete to the browser user, however
    the record in the database does not change. The transaction
    hangs in WebSphere holding an update intent lock in DB2.
    
    The following error message appears in the AppServer:
    
    BBOO0222I: WTRN0108I: ATREINT5. UR state error. Invalid RRS RC:
    731
    The state of the RRS URs for the participants is:
    CICS  - In Forgotten State  (UR gone)
    WebSphere -  In Reset     (UR present)
    DB2 - In Flight   (UR present)
    
    Canceling the Application server cleans up the hung transaction
    and releases the locks to the database.
    
    This apar will address this problem.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Transactional resources not freed       *
    *                      after OLA imported transaction          *
    *                      completes                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a transaction is imported into a WebSphere Application
    Server for z/OS server using the Optimized Local Adapters
    (OLA), WebSphere uses an RRS cascaded UR to connect the OLA
    portion of the transaction to the WebSphere portion of the
    transaction.  The WebSphere cascaded UR is created using the
    ATREINT5 or ATR4EINT service.  The creation of the UR may fail
    if there is a local mode UR present on the context which in
    which the UR is to be created, and the local mode UR is in the
    IN-RESET state.  This can happen if the servant region thread
    just finished processing an application method which runs in a
    local transaction (such as an EJB method with a transaction
    attribute of tx_not_supported), and that local transaction
    accessed an RRS capable resource (such as DB2 using a type 2
    JDBC driver).
    
    The failure is surfaced as a return code 0x731 from the RRS
    service ATR4EINT or ATREINT5.  Return code 0x731 is a UR state
    error.  WebSphere prints the following message in response to
    this return code: BBOO0222I: WTRN0108I: ATREINT5. UR state
    error. Invalid RRS RC:731.  A CORBA::TRANSACTION_ROLLEDBACK
    exception is thrown with minor code C9C2188A.
    
    Eventually the overall transaction will time out and the
    resources will be backed out.  Recycling the application
    server will accelerate this process.
    

Problem conclusion

  • Code was added to ensure that there is not a local mode UR
    present on a context before calling the ATREINT5 or ATR4EINT
    service to begin a cascaded UR.
    
    APAR PM04318 is currently targeted for inclusion in
    Service Level (Fix Pack) 7.0.0.11 of WebSphere
    Application Server
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM04318

  • Reported component name

    WAS OEM EDITION

  • Reported component ID

    5655I3512

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-12-30

  • Closed date

    2010-03-26

  • Last modified date

    2010-07-02

  • 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 FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK57722

       UP10/06/17 P F006

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

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

Document Information

Modified date:
25 October 2021