IBM Support

PI12309: Classes that implement writeobject & readobject calling default writeobject during deserialization are not serialized

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

  • This problem occurs in a situation where a class implements the
    writeObject method and that method invokes defaultWriteObject.
    Instead of using the defaultReadObject
    method to deserialize the object, the readObject method uses
    the readFields deserialize the object. For example, the
    java.util.ConcurrentHashMap in the Java 7 JRE behaves in this
    manner.  This can result in objects not being properly
    recreated during deserialization.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Applications running grids with XIO and     *
    *                  COPY_TO_BYTES enabled.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Classes that implement the              *
    *                      writeObject and readObject that should  *
    *                      call defaultWriteObject, but instead    *
    *                      call readFields.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This problem occurs in a situation where a class implements
    the writeObject method and that method invokes
    defaultWriteObject, and the readObject method uses the
    readFields approach to deserialize the object instead of
    using the defaultReadObject method.  For example, the
    java.util.ConcurrentHashMap in the Java 7 JRE behaves in this
    manner.  This can result in objects not being
    properly recreated during deserialization.
    

Problem conclusion

  • A code change to handle a mixture of serialization formats is
    introduced to address this scenario.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI12309

  • 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

    2014-02-21

  • Closed date

    2014-03-05

  • Last modified date

    2014-03-05

  • 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:
05 March 2014