openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Curtis (Commented) (JIRA)" <>
Subject [jira] [Commented] (OPENJPA-2107) ManagedCache conflict due adding an entity 2 times in the same query.
Date Fri, 13 Jan 2012 23:02:41 GMT


Rick Curtis commented on OPENJPA-2107:

Committed revision 1231375 to trunk.

The root issue is that we only need to reset the Broker flag which indicates if the context
has been flushed when we are initializing a new StateManager.

I'm going to leave this issue Open (and assign it to Heath) as it needs to get fixed in 2.0.x
and 2.1.x.
> ManagedCache conflict due adding an entity 2 times in the same query.
> ---------------------------------------------------------------------
>                 Key: OPENJPA-2107
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 2.2.0
>            Reporter: Mark Struberg
>            Assignee: Rick Curtis
>             Fix For: 2.2.0
>         Attachments: OPENJPA-2107.patch
> I have a complex query which creates the following error:
> <openjpa-2.2.0-tiss-2-rexported nonfatal user error> org.apache.openjpa.persistence.ArgumentException:
Cannot load object with id "26301".  Instance ""
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:
> 	at org.apache.openjpa.kernel.ManagedCache.add(
> 	at org.apache.openjpa.kernel.BrokerImpl.setStateManager(
> 	at org.apache.openjpa.kernel.StateManagerImpl.initialize(
> 	at org.apache.openjpa.kernel.StateManagerImpl.initialize(
> 	at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initializeState(
> It seems that this entity gets loaded from the db twice in the same query.
> While hitting the problem, the StateManagers have the following _flags:
> orig _flags= 602 = 0010 0101 1010 SAVE LOADED READ_LOCKED OID_ASSIGNED FLUSHED  
> sm   _flags= 16  = 0000 0001 0000 READ_LOCKED
> And it is really only 1 instance which makes this problem. If I set the 'orig' variable
to null in the debugger, the test runs fine.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message