I get a NonUniqueObjectException when deleting an object during cleanup in a junit test.

Here are the basic steps:
new session
create object
save object
close session - object is now detached
new session
hql query, loads a different instance of the same object into a list
delete detached copy of the object

This generates a NonUniqueObjectException. If I lock the object, reassociating it with the current session before trying to delete it, the lock causes the NonUniqueObjectException. If I lock the object before running the HQL query, it works fine.

Am I doing something that I shouldn't be? Is there a correct way to reattach an object that may have been otherwise loaded in the interim since it was detached?

Thanks for your help!
Jenica

You cannot have 2 attached instance of the same persistent object (same id). I you load the object and then attach a transiant copy, then it will fail.
You can evict() the already attached object before attaching the other instance.

Emmanuel,

Could you comment on the following post? It sound's like you know what is going on, but from this post, I still don't quite understand what I'm doing wrong.

http://forum.hibernate.org/viewtopic.php?t=933689