PM77477: The xscmd command might not connect if one of the catalogs is unavailable, even with multiple catalog endpoints defined.

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

  • Even when passing in multiple catalog endpoints on the -cep
    option of the xscmd command, a connection failure can occur if
    only one of the catalog servers is not available.
    

Local fix

  • Pass in only available catalog servers on the -cep arguments.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All WebSphere eXtreme Scale users with      *
    *                  multiple catalog servers                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: The xscmd command might fail when a     *
    *                      specified catalog server is not         *
    *                      available.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The getLocationService method would proceed through the
    specified catalog service endpoints. There are two passes to
    find a location service. The first pass occurs for a short
    period of time, 2 seconds. If a location service is not located
    quickly, the endpoints are searched again for a longer
    specified timeout period (the default is 30 seconds).
    If during the first traversal, the first catalog server
    is not reachable, then an exception is returned and the
    remaining catalog servers are not attempted to see if one is
    available.
    However, if the first server is not reached in the time period
    (the network might be slow, since security has increased the
    time required), the next catalog server is attempted, and so
    on. If one of these catalog servers is not reachable,
    then an exception is returned and no other catalog servers are
    attempted.
    

Problem conclusion

  • The command, WXSAdminCatalogConnection:getLocationService,
    was updated to not fail when a catalog server is not available,
    if there are other catalog servers who have not responded
    within the timeout period.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM77477

  • 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

    2012-11-20

  • Closed date

    2012-11-29

  • Last modified date

    2012-11-29

  • 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



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere eXtreme Scale

Software version:

850

Reference #:

PM77477

Modified date:

2012-11-29

Translate my page

Machine Translation

Content navigation