IBM Support

PI12308: Classes with multiple writeObject or readObject methods in a class hierarchy are not deserialized correctly.

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 situations where a class contains multiple writeObject or
    readObject methods in a class hierarchy, the methods of the
    inherited classes were not being invoked. Only the outer-most
    child writeObject or readObject methods are invoked. This can
    result in objects not being properly re-created during
    deserialization.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Applications running data grids with XIO    *
    *                  and COPY_TO_BYTES maps that serialize Java  *
    *                  objects with multiple writeObject or        *
    *                  readObject methods, within a class          *
    *                  hierarchy.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Classes with multiple writeObject or    *
    *                      readObject methods in a class           *
    *                      hierarchy are not deserialized          *
    *                      correctly.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In situations where a class contains multiple writeObject or
    readObject methods in a class hierarchy, the methods of the
    inherited classes were not being invoked. Only the outermost
    child writeObject or readObject methods are invoked. This can
    result in objects not being properly re-created during
    deserialization.
    

Problem conclusion

  • A new serialization format that handles this particular
    scenario was introduced to address this situation. Update
    clients and servers to use the serialization format.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI12308

  • 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-03

  • Last modified date

    2014-03-03

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