IBM Support

PI52838: OptimisticCollisionException fails to deserialize when using EntityManager

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

  • When the server has an association that the client isn't aware
    of, the key can fail to deserialize.  The exception will appear
    similar to below.
    
    Caused by:
    com.ibm.ws.xsspi.xio.exception.ObjectGridXIOException: An
    exception was received from the server, but it could not be
    processed from the ServerException message. exception_type:
    TRANSACTION_EXCEPTION
    exception_id: 44666
    exception_message:
    "com.ibm.websphere.objectgrid.TransactionException:transaction
    rolled back, see caused by Throwable"
    endpoint_id: "44167150216b981fe000005056050080"
    completed: true
    class_name: "com.ibm.websphere.objectgrid.TransactionException"
    caused_by {
      exception_type: OPTIMISTIC_COLLISION
      exception_id: 44665
      exception_message:
    "com.ibm.websphere.objectgrid.plugins.OptimisticCollisionExcepti
    on:Optimistic version comparison indicates another transaction
    already changed this cache entry.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of eXtreme Scale who use              *
    *                  EntityManager with different associations.  *
    ****************************************************************
    * PROBLEM DESCRIPTION: When trying to deserialize an entity    *
    *                      and there are not as many associations  *
    *                      as expected, deserialization fails.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The entity deserialization logic was updated to handle an
    expected association not being in the stream.  Additionally,
    OptimisticCollisionException processing on the server side was
    updated to use the key that was provided from the client,
    instead of the key that is currently in the grid.
    

Problem conclusion

  • An interim fix is available for this APAR upon request.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI52838

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-11-19

  • Closed date

    2016-01-11

  • Last modified date

    2016-01-11

  • 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:
11 January 2016