Ok.. Suppose we have two node: Node 'A' e Node 'B'.
In the persistence context of Node 'A' and Node 'B' there is an Entity Instance 'E'.
If Node 'A' remove 'E' and Node 'B' persistence context don't know about this, when 'B' try to make a merge to 'E', 'B' find the instance 'E' and TopLink transforms merge operation (at commit time) in an UPDATE query.. So database can't find E primary key and the entity 'E' data merged by 'B' node is lost.
What are the solutions?
Glassfish Cluster do anything to avoid this?
[Message sent by forum member 'peppeme' (peppeme)]
http://forums.java.net/jive/thread.jspa?messageID=266377