PM76020: Serialization errors when using the COPY_TO_BYTES copy mode after restarting the data grid and not restarting the client.

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 following exception occurs in the server logs:
    
    CWOBJ0002W: ObjectGrid component, Session
    [DOMAIN_NAME:GRID_NAME:IBM_SYSTEM_ENTITYMANAGER_MAPSET:0],
    is ignoring an unexpected exception:
    com.ibm.websphere.objectgrid.ObjectGridRuntimeException:
    java.io.NotSerializableException:
    com.ibm.ws.objectgrid.plugins.SerializationInfoKey
    at
    com.ibm.ws.objectgrid.map.LogSequenceDataImpl.marshal(LogSequenc
    eDataImpl.java:76)
    
    Additionally get operations can fail with EOFException,
    StreamCorruptedException, ClassCastException, and other
    IOExceptions.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of eXtreme Scale who use the      *
    *                  COPY_TO_BYTES function with the built-in    *
    *                  ObjectTransformer, instead of using a       *
    *                  custom transformer or serializer            *
    ****************************************************************
    * PROBLEM DESCRIPTION: When the value object was converted     *
    *                      to bytes after a grid restart, data     *
    *                      can be corrupted because of old meta    *
    *                      data being used.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When an entire data grid is stopped and the clients are left
    running (which may include the monitoring console), the client
    tries to synchronize with the meta data between the client and
    the server.  There were errors in the logic for getting the
    meta
    data in sync, which caused the NotSerializableException
    exception.
    Additionally if a value was already serialized with the old
    meta
    data and the synchronization process determined that the
    server had newer meta data that the client should use, the
    value object was not being re-serialized with the updated meta
    data.
    

Problem conclusion

  • An interim fix is available for this problem and the fix is
    incorporated in the next fix pack for 7.1.1 and 8.5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM76020

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    711

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-29

  • Closed date

    2012-11-29

  • Last modified date

    2012-11-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

  • R711 PSY

       UP

  • R850 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere eXtreme Scale

Software version:

711

Reference #:

PM76020

Modified date:

2012-11-29

Translate my page

Machine Translation

Content navigation