IBM Support

PI05212: Clients with short client retry timeouts experience TargetNotAvailable exceptions during server restart.

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 servers restart after it stops or fails over, clients with
    short retry settings (for example, 5 seconds or less) can
    experience TargetNotAvailable exceptions instead of routing
    quickly to the primary shards that are balanced to the
    restarted servers.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere eXtreme Scale users running       *
    *                  with short client retry time experience     *
    *                  TargetNotAvailable exceptions during server *
    *                  restart.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Clients with short client retry         *
    *                      timeouts experience exceptions when     *
    *                      servers are restarted and shards        *
    *                      balance to new servers.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When shards move to newly started servers, some existing
    clients do not get the updated route entries before the short
    retry timeouts (example, the client property
    requestRetryTimeout is set to 5 seconds). The clients
    experience unexpected TargetNotAvailable exceptions.
    The TargetNotAvailable exceptions indicate that the client
    could not find the correct endpoint; for example:
    BaseMap W CWOBJ0006W: An exception occurred:
    com.ibm.websphere.objectgrid.ObjectGridRuntimeException:
    com.ibm.websphere.objectgrid.TargetNotAvailableException:
    Retrying the request expired, the current timeout is set to
    4000 (ms). domain1:Grid:mapSet:591 forward: true
    

Problem conclusion

  • Apply the fix. To work around this exception, extend the
    requestRetryTimeout property to a longer timeout. The
    TargetNotAvailable exceptions resolve after a short period of
    time.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI05212

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-10-31

  • Closed date

    2013-11-08

  • Last modified date

    2013-11-08

  • 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

  • R850 PSY

       UP

  • R860 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"860","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
08 November 2013