Thank you very much, Michael!
That solved the issue.
Regards,
Anvay
From: eclipselink-users-bounces@xxxxxxxxxxx [mailto:eclipselink-users-bounces@xxxxxxxxxxx]
On Behalf Of Michael Hönnig
Sent: Friday, September 04, 2015 11:58 AM
To: eclipselink-users@xxxxxxxxxxx
Subject: Re: [eclipselink-users] Cache coordination issue - Eclipselink merge command creating uninitialized object on remote servers
I've seen similar problems with the EclipseLink cache, even without cache coordination, where uninitialized entity instances had been cloned from the cache. Might be the same defect.
For cache coordination I suggest to use invalidation over sending the objects. See @Cache( coordinationType=...). That should already solve that problem. There are rare cases where SEND_OBJECT_CHANGES is needed, which unfortunately is the default.
You also might need to use @OptimisticLocking(cascade=true). Otherwise insertion+deletion in lists of the owning entity might not always be recognized on the other nodes.
Best regards
Michael
--
http://michael.hoennig.de
This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee
is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the material from any computer.
|
