IBM Support

PM64335: JPA ERROR DURING PERSISTING COLLECTION WITH CASCADE PERSIST AFTER FLUSH

Fixes are available

7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • JPA Error during persisting collection with cascade persist
    after flush
    
    Namely some items added to collection after flush occurred
    during transaction are not persisted. Some means that
    when we add more than one item only first is persisted.
    
    Debugging indicates it is the same or at least very similar
    issue to OPENJPA-2051 even when we are using 1.* branch of
    openjpa.
    
    This APAR addresse the following  JPA defects -
    https://issues.apache.org/jira/browse/OPENJPA-2051
    https://issues.apache.org/jira/browse/OPENJPA-2107
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0.0 and V8.0.0 who rely           *
    *                  on a cascade persist during a flush to the  *
    *                  database.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: OpenJPA ManagedCache conflict due to    *
    *                      adding an entity two times in the       *
    *                      same query.                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The OpenJPA ManagedCache (L1 cache) has a bug which cause the
    following exception when a persist is cascaded during a flush:
    <openjpa-2.2.0 nonfatal user error>
    org.apache.openjpa.persistence.ArgumentException: Cannot load
    object with id "26301". Instance
    "com.xxx.xx.entities.DefaultCourse@6e267b76" with the same id
    already exists in the L1 cache. This can occur when you assign
    an existing id to a new instance, and before flushing attempt
    to load the existing instance for that id.
    FailedObject:
    com.xxx.xx.entities.DefaultCourse-26301
    at
    org.apache.openjpa.kernel.ManagedCache.add(ManagedCache.java:126
    )
    at
    org.apache.openjpa.kernel.BrokerImpl.setStateManager(BrokerImpl.
    java:4117)
    at
    org.apache.openjpa.kernel.StateManagerImpl.initialize(StateManag
    erImpl.java:391)
    at
    org.apache.openjpa.kernel.StateManagerImpl.initialize(StateManag
    erImpl.java:340)
    at
    org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initializeState(
    JDBCStoreManager.java:378)
    This occurs when flushing a complex graph of entities.  The
    scenario and entity graph is similar to that as described in
    APAR PM48637.  The main difference is in the test scenario.
    That is, the problematic pattern is to create an entity
    instance, persist it, and do a query containing this new
    entity in the same transaction in which it was created.  This
    causes OpenJPA to attempt to put the instance into the L1
    cache multiple times, thus yielding the ArgumentException.
    

Problem conclusion

  • With this fix, code has been added to ensure entities are not
    added to the cache multiple times and are properly cascaded for
    the scenario described.
    
    The fix for this APAR is currently targeted for
    inclusion in Service Levels (Fix Packs) 7.0.0.25 and 8.0.0.5
    
    of WebSphere Application Server versions 7.0.0 and 8.0.0.
    
    Please refer to the recommended updates page for delivery
    information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM64335

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-09

  • Closed date

    2012-06-25

  • Last modified date

    2012-07-17

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PM65343

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM64335

Modified date: 17 July 2012