IBM Support

PI49299: getObjectGridState API does not return a consistently correct result when grid is in transition

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

  • getObjectGridState occasionally returns and incorrect state.
    For example, when the grid is coming online, this API might
    return a state of ONLINE before all of the partitions within
    the grid are actually on-line.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of the                            *
    *                  StateManager.getObjectGridState() API.      *
    ****************************************************************
    * PROBLEM DESCRIPTION: During grid startup, the                *
    *                      StateManager.getObjectGridState() API   *
    *                      will at times incorrectly report an     *
    *                      ONLINE state.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During grid startup, the StateManager.getObjectGridState() API
    will occasionally report that all partitions are ONLINE state
    even when the grid has not completed startup activity.
    

Problem conclusion

  • The code was changed to ensure that all partitions within the
    grid report the ONLINE status before that status is returned
    to the caller.
    
    An interim fix against the 8.6.0.8 service release containing
    this change is available upon request from IBM support.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI49299

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-09-24

  • Closed date

    2015-11-05

  • Last modified date

    2016-09-01

  • 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

  • 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:
01 September 2016