Hello, I'm encountering this bug, but with a different stack than the one
reported in https://cwiki.apache.org/jira/browse/OPENJPA-1001.
I'm using OpenJPA 1.3.0-SNAPSHOT and am accessing it through OpenEJB. I
will attempt to reproduce this bug with a simpler test case than the one I'm
currently running, but felt that given the priority of the bug I'd report
what I could at the moment.
Here is a snippet of the stack:
Caused by: <openjpa-1.3.0-SNAPSHOT-r422266:803348 nonfatal general error>
org.apache.openjpa.persistence.PersistenceException: Index: 3, Size: 3
at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:877)
at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:776)
at org.apache.openjpa.kernel.BrokerImpl.isDetached(BrokerImpl.java:4289)
at
org.apache.openjpa.kernel.VersionAttachStrategy.attach(VersionAttachStrategy.java:78)
at
org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:251)
at
org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:104)
at org.apache.openjpa.kernel.BrokerImpl.attach(BrokerImpl.java:3215)
at
org.apache.openjpa.kernel.DelegatingBroker.attach(DelegatingBroker.java:1158)
at
org.apache.openjpa.persistence.EntityManagerImpl.merge(EntityManagerImpl.java:769)
at
org.apache.openejb.persistence.JtaEntityManager.merge(JtaEntityManager.java:102)
This results from a simple merge() call on an entity that has not been
persisted before. Looking through the stack, perhaps it is also relevant
that my entities at the moment do not have @Version fields.
I hope this helps someone out in rooting around to get to the bottom of it;
this is kind of blocking me--is there a workaround?
Thanks,
Laird
