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

Fixes are available

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?