Can you post the trace file somewhere so I can take a look?
On Tue, Oct 29, 2013 at 4:48 PM, Givanildo Dantas Alves <[email protected]>wrote: > A ConcreteRecord is a joint of AliasRecords. It has some OneToMany > relationships, to enable association with AliasRecords and with some data > that come from AliasRecords. > A new AliasRecord is associated to an existing ConcreteRecord or a to brand > new one, according to a set of criteria > AliasRecords IDs are automatically generated (GeneratedValue annotation). > On > the other hand, ConcreteRecord ID is same as the ID of one its associated > AliasRecords. > > All the work is done inside a transaction. By the way, with the addition of > a call to EntityManager flush() method, the problem still happens. > > ConcretedRecord and AliasRecords don't have @Version fields. I have > MappedSuperclass with that annotation, but the corresponding entities don't > seem related to the current issue. > > I am not sure what that merge() call is for. Good question. That does not > seem required. I can remove that call and run some tests, even though > successful executions would not necessarily tell me that the problem was > resolved. > > > Thanks > > > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/Intermittent-EntityNotFoundException-for-loading-of-ID-field-tp7585392p7585456.html > Sent from the OpenJPA Developers mailing list archive at Nabble.com. > -- *Rick Curtis*
