IBM Support

PI14525: The listener, JMSObjectGridEventListener, fails when running with synchronous replication.

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

  • JMSObjectGridEventListener fails to update clients with the
    following message and exception stack:
    
    CWOBJ0024E: Cannot deserialize field 1241519472 in class
    com.ibm.ws.objectgrid.map.LogSequenceImpl.  Deserialization
    failed.
    
    java.io.IOException:   Invalid stream content (end) for
    Collection of LogSequences.
    at
    com.ibm.ws.objectgrid.map.LogSequenceImpl.inflate(LogSequenceImp
    l.java:3401)
    at
    com.ibm.websphere.objectgrid.plugins.LogSequenceTransformer.infl
    ate(LogSequenceTransformer.java:128)
    at
    com.ibm.websphere.objectgrid.plugins.builtins.JMSObjectGridEvent
    Listener.run(JMSObjectGridEventListener.java:1230)
    at java.lang.Thread.run(Thread.java:773)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of eXtreme Scale who are using    *
    *                  the COPY_TO_BYTES CopyMode with the         *
    *                  JMSObjectGridEventListener with             *
    *                  synchronous replication enabled.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: When deserializing LogSequences with    *
    *                      the JMSObjectGridEventListener, an      *
    *                      IOException exception occurs.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A logic error for how a LogSequence is serialized when
    using COPY_TO_BYTES prevented the correct data from being
    serialized for a LogSequence object.  When the receiver of the
    serialized LogSequence tried to inflate it, it failed due to
    the format not being what was expected.
    

Problem conclusion

  • An interim fix is available for this APAR.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI14525

  • 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

    2014-03-26

  • Closed date

    2014-04-15

  • Last modified date

    2014-04-15

  • 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:
15 April 2014