Description of problem:
The hibernate detach utility fails to correctly detach hibernate objects when both self referencing and identity conflicts occur at the same time.
The following message can be seen in the logs. Increasing the allowed depth does not solve the problem.
WARN [org.rhq.enterprise.server.safeinvoker.HibernateDetachUtility] Recursed too deep [101 > 100], will not attempt to detach object of type [org.rhq.core.domain.resource.InventoryStatus]. This may cause serialization errors later. If so, you can try to work around this by setting the system property [rhq.server.hibernate-detach-utility.depth-allowed] to a value higher than .
The hopeful fix is in.
!!! commit commit 8c77babdf5f14c6a4161833c06ca6cf944d630a8
Fixes a problem in the above commit.
added a new unit test to see that the fix works. master commit 90f0867
I did verify that without the fix, this test would fail.
Nothing QA can do to test this. Its a code change only that the unit test will
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE