3

I have an error when I want to delete an object from database. The error is:

org.hibernate.NonUniqueObjectException: a different object with the same identifier value was already associated with the session: [com.cartif.database.ApplicationField#asd]

To delete an object I do:

public static void delete(Object o){
    if(session == null) createSession();
    Transaction tx = session.beginTransaction();
    tx.begin();
    session.delete(o);
    tx.commit();
}

When I call this method with an object, I obtain the error. If I debug the application the exception is thrown in tx.begin(); line.

On database this object is unique, as I show in the columns:

         name                   deviceid
         "asd"                     1
"ElectricalConsumption"            1
       "Energy"                    1

Why is that happened?

Thanks in advance!

Jose Hdez
  • 2,297
  • 7
  • 38
  • 52

2 Answers2

4

NonUniqueObjectException is thrown when there is an object already associated with the session with the same id (primary key) as the one you are trying to associate with session.

This generally has nothing to do with the delete method itself and has more to do with the context in which the delete is called

Check the place where the delete is called. Check for any possible duplicate objects in the place where the delete is called.

This question may also help.

Community
  • 1
  • 1
Nivas
  • 18,126
  • 4
  • 62
  • 76
  • 1
    But how can I solve the problem? I have tried with session.close(), session = null; and create a new session, session.clear(), but it does not work. – Jose Hdez Jun 29 '11 at 11:11
  • What to do depends on your situation. If you have an object (say from the UI layer) and doing a find by PK on it, and then trying to delete it, then you can call the delete directly on it. You may also want to try `session.flush()`. You can try merging you both objects (if you have identified them, that is). The solution completely depends on context. – Nivas Jul 01 '11 at 08:20
0

This error indicates that you have loaded the same object (here same implies that both objects have the same identifier value) more than once in the same session. It doesn't have anything to do with the uniqueness in the database.

Sriram
  • 838
  • 7
  • 15