IBM Support

PM80350: The catalog server does not retry timed out, placement service work.

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

  • The catalog server sends placement work to a container.  If the
    work does not complete in time or if the container server does
    not receive the work request, then the catalog server does not
    retry. This behavior stops the shard containers from being
    successfully placed and can lead to other errors in the
    data grid.
    
    In the catalog placement trace, workTimedout entries are
    displayed.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Any eXtreme Scale user, especially those    *
    *                  with larger grids                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: Potentially heavy eXtreme               *
    *                      Scale processing can occur on           *
    *                      object request broker (ORB) threads.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The processing needed in the catalog server to include a
    container for potential placement can be non-trivial.
    Therefore, as the number of containers in a domain increase,
    this processing can put a strain on the ORB thread pools.
    However, after the message is received in the catalog, the
    processing needed to include the given container for placement
    can occur on a separate thread.
    

Problem conclusion

  • A fix is provided to offload the ORB thread and subsequently,
    run processing on a specific eXtreme Scale thread.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM80350

  • 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-01-10

  • Closed date

    2013-01-31

  • Last modified date

    2013-01-31

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

Document Information

Modified date:
31 January 2013