An issue in this release of JBoss EAP 6 could result in an `java.lang.IllegalStateException: An entity copy was already assigned to a different entity` error being encountered.
The issue presents during a cascade merge if multiple entity instances with the same identity are detected. As they cannot be automatically merged, the exception is raised.
This issue is expected to be resolved in a future release of the product.
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
*** Bug 1095185 has been marked as a duplicate of this bug. ***
Is this still planned for 6.3.0?
There are some known issues related to this fix. They should probably be included in release notes. I've also added HHH-9216 for adding documentation about this fix to the upstream documentation. Should that also be included in Hibernate doc for EAP?
I'm not sure if I can finish that by Wednesday. Can it be deferred? I'm still getting up-to-speed on EAP processes, so I'm unsure of the impact on the one-off. Can someone provide guidance about this?
New JIRA issue for backporting HHH-9106 to 4.2 branch is HHH-9261.
Fixed for 6.4.0.
Fixed by Hibernate 4.2.16.Final upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1121629
verified on EAP 6.4.0.DR11 / Hibernate 4.2.16