IBM Support

PI07377: Primary shards hang during placement when ObjectGridEventListeners and sync replicas are configured.

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

  • Primary shards hang during placement when data grid event
    listeners and synchronous replicas are configured.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere eXtreme Scale users running with  *
    *                  synchronous replication,                    *
    *                  ObjectGridEventListeners, and template      *
    *                  maps.                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: When placing or promoting primary       *
    *                      shards, some or all of primary shards   *
    *                      do not open for traffic.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The primary shard appears in the xscmd routetable output, but
    clients experience TargetNotAvailableExcepions from the
    org.omg.CORBA.TRANSIENT package. The issue occurs when
    synchronous replication is configured and the data grid has an
    ObjectGridEventListener defined. The shardActivated
    method for the event listener must also create new template
    maps.
    The primary shard hangs during its startup. The JVM log
    of the primary shard can contain a COWBJ1574I message
    indicating long activation time. The CWOBJ1574I message
    includes a stack dump. For this issue, the stack includes the
    class and method:
    com/ibm/ws/objectgrid/replication/PrimaryShardImpl.mapCreated.
    A Java core dump of the container processes contain the same
    stack.
    

Problem conclusion

  • To workaround, do not create template maps in an
    ObjectGridEventListener shardActivated method, or do not use
    synchronous replication. Apply the fix associated with this
    APAR.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI07377

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

  • Closed date

    2013-12-12

  • Last modified date

    2013-12-12

  • 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:
12 December 2013