[ https://issues.apache.org/jira/browse/OPENJPA-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Curtis updated OPENJPA-2107:
---------------------------------

    Attachment: OPENJPA-2107.patch

Mark -

It looks like we put this bug in with OPENJPA-2051. Give this patch a try.

Note, I haven't had time to try to run this patch through the entire test bucket yet.
                
> ManagedCache conflict due adding an entity 2 times in the same query.
> ---------------------------------------------------------------------
>
>                 Key: OPENJPA-2107
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2107
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 2.2.0
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             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 "at.ac.tuwien.tiss.curriculum.be.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: at.ac.tuwien.tiss.curriculum.be.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(StateManagerImpl.java:391)
> 	at org.apache.openjpa.kernel.StateManagerImpl.initialize(StateManagerImpl.java:340)
> 	at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initializeState(JDBCStoreManager.java:378)
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira