javax.persistence.EntityExistsException: a different object with the same identifier value was already associated with the session

Question

I have two entities (A & B). A has one to many relation with the entity B. Primary key of the entity A is auto increment where as the primary key of entity B is composite (consisting of PK of entity A as a foreign key and one auto incremented id).

Note: I am using EJB 3.1 with MySQL, Jboss7

I populate the entity A from my business objects and create it in the following way.

A a = new A();
Set<B> bEntitiesList = new HashSet<B>();
B b = new B();
b.setCompositeKey(new compositeKey()); // I am not setting any value in the 
// key and it will have null values for idA and idB.
// idB is null because it will be auto incremented in this table by MySQL
bEntitiesList.put(b);
a.setBEntities(bEntitiesList);
entityManager.persist(a);

Whenever I pass one object of Entity B in the bEntities list then the program works as expected all the fields in the database are populated correctly but when i add more than one object entity B in the bEntities list then I get the exception "javax.persistence.EntityExistsException: a different object with the same identifier value was already associated with the session". I am not sure how to work around this one. The message clearly says that the hibernate session has found duplicate entries (which is due to the fact that compositekey has overriden methods generated by default by MyEclipse which generates the same hashcode but I am not sure this is causing the problem). Kindly tell me how can i solve this. Is there a need to override the equals and hashcode methods in the compositekey class? Thanks in advance.

public class A
{
    private Integer idA;
    private Set<B> bEntities = new HashSet<B>(0);
    @Id
    @GeneratedValue(strategy = IDENTITY)
    @Column(name = "A", unique = true, nullable = false)
    public Integer getIdA() {
      return this.idA;
    }
    @OneToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY, mappedBy = "A")
    public Set<B> getBEntities() {
      return this.bEntities;
    }
}

public class B
{
    private compositeKey key;
    private A entityA;
    @EmbeddedId
    @AttributeOverrides({
    @AttributeOverride(name="idB",column=@Column(name="idB",nullable=false))})
    public compositeKey  getKey() {
       return this.key;
    }
    public void setKey(compositeKey key) {
      this.key = key;
    }
    @ManyToOne(fetch = FetchType.LAZY)
    @MapsId("providerReferenceNo")
    @JoinColumn(name = "idA", nullable = false, insertable = false, updatable = false)
    public A getEntityA() {
      return this.entityA;
    }
}


@Embeddable
public class compositeKey {
private Integer idA;
private Integer idB;

@GeneratedValue(strategy = IDENTITY)
@Column(name = "idB", nullable = false)
public Integer getIdB() {
  return this.idB;
}
@Column(name = "idA", nullable = false)
public Integer getIdA() {
  return this.idA;
}

http://stackoverflow.com/questions/1074081/hibernate-error-org-hibernate-nonuniqueobjectexception-a-different-object-with ? — Michael Wiles, Aug 27 '13 at 14:50
Thanks Micheal.. I have seen the post already. I have debugged the application and I found that whenever I create a single object of compositeKey then it gets a hashcode of lets say ab871c and it is saved properly in the database but when I create multiple objects; all the objects get the same hashcode i.e. ab871c. Why I am getting this behavior? Is it because both the fields in the compositeKey are null? Is there workaround available for this? — Sam ツ, Aug 27 '13 at 16:38

score 1 · Answer 1 · answered Aug 28 '13 at 10:21

1

I think your issue may have something to do with how the hashCode/Equals does not correspond to the objects identity according to JPA/EJB3.1.

Try and add the hashCode/Equals methods to B and also change that bEntities to a List - or if you keep it a set then ensure that the data that hashCode/Equals uses before it is added to the set is hydrated. You should probably do this by adding hashCode and equals methods to CompositeKey and deffering to them in B's hashcode and equals.

Btw, you must add hashCode and Equals methods to CompositeKey. One of the reason for using a CompositeKey is to tell the persistence framework how to compare to composite keys.

answered Aug 28 '13 at 10:21

Michael Wiles

20,902
18
71
101

hashCode and equals methods are already overridden in compositeKey class but the implementation is the default one (which was provided by MyEclipse when I generated the entities and facades). What do you mean by "You should probably do this by adding hashCode and equals methods to CompositeKey and deffering to them in B's hashcode and equals." Personally I think the same that there's an issue how the hashCode/equals correspond to object identity in JPA/EJBs 3.1. Where I can find that how JPA/EJB3.1 identify the duplicate entities in the session? What is the criteria? – Sam ツ Aug 28 '13 at 11:35
does B have hashCode and Equals? – Michael Wiles Aug 28 '13 at 11:51
No, B doesn't have hashCode & equals. – Sam ツ Aug 28 '13 at 12:18
Will it be a good idea to change the hashCode method and generate random numbers every time? What do you say? – Sam ツ Aug 28 '13 at 12:19

javax.persistence.EntityExistsException: a different object with the same identifier value was already associated with the session

1 Answers1