PM79767: Intermittent timing issues can occur when containers start and cause placement to occur prematurely.

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

  • In large environments when you run the xscmd resumeBalancing
    command, or when a large number of containers have been
    started and balancing begins, there can be a bottleneck of work
    in the object request broker (ORB) thread pool.
    
    Most of the ORB threads from the Java core file process the
    checkEpochForObjectGridRouteInfo message:
    
    .
    .
    .
    
    at
    com.ibm.ws.objectgrid.objectMapping.ObjectBytes.bytesToObject(Ob
    jectBytes.java:169)
    at
    com.ibm.ws.objectgrid.catalog.placement.ReadOnlyCatalogServiceIm
    pl.copyObjectGridEndpoint(ReadOnlyCatalogServiceImpl.java:274)
    at
    com.ibm.ws.objectgrid.catalog.placement.ReadOnlyCatalogServiceIm
    pl.checkEpochForObjectGridRouteInfo(ReadOnlyCatalogServiceImpl.j
    ava:131)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Any eXtreme Scale user who runs the         *
    *                  suspend and resume placement function.      *
    ****************************************************************
    * PROBLEM DESCRIPTION: If a data grid is suspended before      *
    *                      the hosting containers start, then      *
    *                      placement can occur prematurely.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Intermittent timing issues during container startup overrides
    the suspend placement setting, and can cause placement to
    occur prematurely.
    

Problem conclusion

  • A fix has been included to honor the suspension of placement
    during the initial start of a data grid.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM79767

  • 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-12-28

  • Closed date

    2013-01-29

  • Last modified date

    2013-01-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

Document information


More support for:

WebSphere eXtreme Scale

Software version:

850

Reference #:

PM79767

Modified date:

2013-01-29

Translate my page

Machine Translation

Content navigation