IBM Support

PI93971: CR TERMINATES AFTER WTRN0108I: CONTEXTDISASSOCIATION. UNEXPECTED STATE: 3 AND FAILEDXARESOURCES = TRUE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The control region encounters an unexpected condition while
    completing a JTA transaction and issues a message of the form:
    BBOO0222I: WTRN0108I: contextDisassociation. Unexpected state:
    3 ... ,FailedXAResources = true, ...
    
    It then terminates with:
    BBOO0035W TERMINATING THE CURRENT PROCESS, REASON=C9C21A30.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server on z/OS                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Control Region terminates issuing       *
    *                      WTRN0108I: contextDisassociation.       *
    *                      Unexpected state: 3 ...                 *
    *                      ,FailedXAResources = true ...           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When completing a JTA transaction involving multiple XA
    Resources, a performance optimization was used because all but
    one XA Resource voted read-only.  However, when the commit
    request was sent to the single XA Resource, it failed with an
    XAException with error code XA_RETRY.  The error handling code
    for the performance optimization was incorrect, resulting in an
    unexpected state during context disassociation, which in turn
    caused the transaction service to terminate the control region.
    

Problem conclusion

  • The error handling for the performance optimization was
    changed so that the retry process for transaction completion
    was configured and initiated correctly.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.14 and 9.0.0.9.  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

    PI93971

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-02-19

  • Closed date

    2018-05-18

  • Last modified date

    2018-05-18

  • 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

  • R800 PSY

       UP

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

Document Information

Modified date:
19 October 2021