PM92924: Transactions are not marked as active for rollback in fail fast scenarios.

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

  • Transactions are not marked as active for rollback in fail fast
    scenarios.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere eXtreme Scale users that are      *
    *                  running                                     *
    *                  with low or no client retry values and are  *
    *                  experiencing client request timeouts such   *
    *                  as                                          *
    *                  NO_RESPONSE or MessageTimeOutException.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: During the early NO_RESPONSE or         *
    *                      MessageTimeOutException exceptions,     *
    *                      the transactions that fail are not      *
    *                      properly marked to roll back. When      *
    *                      the client later attempts to access     *
    *                      the same keys that were used by the     *
    *                      failed transaction, they are still      *
    *                      locked                                  *
    *                      by the prior transaction. The later     *
    *                      requests also receive NO_RESPONSE or    *
    *                      MessageTimeOutException exceptions.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A client that is running in fail-fast mode receives a
    NO_RESPONSE or
    MessageTimeOutException during a failure event. The failure
    event might be a lost server or network problem.  The client
    continues to receive exceptions after the
    failover recovers and the catalog service domain appears to be
    healthy. A fail-fast scenario includes a client with a very
    low or no client retry value set. For example, the client
    property,
    requestRetryTimeout, is set to -1 or less than the Object
    Request Broker (ORB) requestTimeout property or the IBM
    eXtremeIO (XIO) xioRequestTimeout property.
    

Problem conclusion

  • After the inital NO_RESPONSE or MessageTimeOutException, any
    outstanding transactions should automatically roll back when
    they reach their transaction timeout value. If no transaction
    timeout value is set, the default is 10 minutes. Apply the inter
    fix to allow transactions to roll back properly in this scenario
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM92924

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-07-12

  • Closed date

    2013-07-22

  • Last modified date

    2013-07-22

  • 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

    WS EXTREME SCAL

  • Fixed component ID

    5724X6702

Applicable component levels

  • R711 PSY

       UP

  • R850 PSY

       UP

  • R860 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere eXtreme Scale

Software version:

850

Reference #:

PM92924

Modified date:

2013-07-22

Translate my page

Machine Translation

Content navigation