IBM Support

PH50987: INCORRECT BEHAVIOR WHEN ROLLBACK TRANSACTION AFTER TIMEOUT

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When a transaction timeout occurs in a subordinate, an
    unnecessarily large delay can occur between the transaction
    timing out and the transaction itself being rolled back.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Subordinate transaction may not         *
    *                      rollback in a timely fashion            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a transaction times out, the timeout thread will first
    attempt to abort connections and, if the transaction is not
    currently active on another thread, rollback resources.  It
    will then schedule a rollback of the transaction after a
    delay.  If the scheduled transaction rollback cannot complete,
    it will also be re-scheduled using the same delay.
    The delay used for scheduling the transaction rollback was the
    timeout duration of the transaction.
    For example, if the transaction timeout was 5 minutes then the
    initial attempt to rollback the transaction would only occur 5
    minutes after the transaction had timed out.
    This issue is not present on WebSphere Application Server for
    z/OS.
    

Problem conclusion

  • The transaction's timout duration should not have been used by
    the timeout process for the delay when scheduling the
    transaction rollback attempts.  The delay value has been
    changed.
    
    The fix for this APAR is targeted for inclusion in fix packs
    8.5.5.26 and 9.0.5.21. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH50987

  • 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

    2022-11-17

  • Closed date

    2024-06-19

  • Last modified date

    2024-06-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

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
19 June 2024