Are you getting a Concurrent Modification exception or an Optimistic
Lock exception? If you are getting a concurrent modification exception
it sounds like you may be modifying the object passed to the merge
operation in a separate thread. Can you provide the stack trace.
--Gordon
Witold Szczerba wrote:
> Hello there,
> as I can see in my project, entityManager throws Concurrent
> modification exception when I am using merge on non-existing entity
> when it's @Version field is null.
> I read that #merge should act pretty like the same as #persist when
> given entity doesn't exist and ToplinkEssentials implementation does
> not work that way.
> Is that correct behavior?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>