IBM Support

PK32350: TRANSACTION_ROLLEDBACK EXCEPTION WHEN REQUEST ROUTED TO QUIESCING SERVER AND DOES NOT GET RE-ROUTED TO ANOTHER SERVER.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • TRANSACTION_ROLLEDBACK EXCEPTION when requested routed to
    quiescing server and does not get re-routed to another server.
    
    The problem is that when a remote request directed to a cluster
    is routed to a server that is quiescing (and the server has not
    seen the transaction before), the request does not get
    re-routed to another server in the cluster, but the transaction
    is rolled back with a TRANSACTION_ROLLEDBACK EXCEPTION.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All WebSphere Application Server version 6   *
    *                 users.                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Unexpected TRANSACTION_ROLLEDBACK       *
    *                      exception when server is in quiesce     *
    *                      stage of shutdown.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    TRANSACTION_ROLLEDBACK EXCEPTION when request routed to
    quiescing server and does not get re-routed to another server.
    When routing a request to a clustered server, and the request
    fails, it is expected that if there is no transaction affinity
    with the server then the request should be routed to another
    server in the cluster.
    However, if the server is quiecing, the request does not get
    re-routed as expected. Instead the transaction in the
    originating server is rolled back, before Work Load Manager
    can re-route the request.
    

Problem conclusion

  • This fix changes the class TxClientInterceptor to ensure that
    if the remote request receives a SystemException with a minor
    code of WLM_SERVER_QUIESCE then the transaction will not be
    rolled back, and so give Work Load Manager the chance to
    re-route the request.
    The fix for this APAR is currently targeted for inclusion in
    fixpack 6.0.2.19 for version 6.0 and 6.1.0.9 for version 6.1.
    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

    PK32350

  • Reported component name

    WEBSPH APP SERV

  • Reported component ID

    5724J0800

  • Reported release

    60A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-10-04

  • Closed date

    2007-03-01

  • Last modified date

    2007-03-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • TRAN
    

Fix information

  • Fixed component name

    WEBSPH APP SERV

  • Fixed component ID

    5724J0800

Applicable component levels

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z 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":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021