Found shared references to a collection org hibernate HibernateException

Question

I got this error message      error  Found shared references to a collection  Person relatedPersons   When I tried to execute addToRelatedPersons anotherPerson    person addToRelatedPersons anotherPerson   anotherPerson addToRelatedPersons person    anotherPerson save    person save      My domain   Person     static hasMany    relatedPersons Person        any idea why this happens

User · Answer

I too got the same issue  someone used BeanUtils copyProperties source  target   Here both source and target  are using the same collection as attribute    So i just used the deep copy as below    How to Clone Collection in Java - Deep copy of ArrayList and HashSet

User · Answer

Consider an entity   public class Foo  private lt user gt  user     with getters and setters        And consider an Business Logic class   class Foo1  List lt User gt  user   new ArrayList lt  gt     user   foo getUser        Here the user and foo getUser   share the same reference  But saving the two references creates a conflict    The proper usage should be   class Foo1   List lt User gt  user   new ArrayList lt  gt     user addAll foo getUser       This avoids the conflict

User · Answer

Posting here because it s taken me over 2 weeks to get to the bottom of this  and I still haven t fully resolved it  There is a chance  that you re also just running into this bug which has been around since 2017 and hasn t been addressed  I honestly have no clue how to get around this bug  I m posting here for my sanity and hopefully to shave a couple weeks of your googling  I d love any input anyone may have  but my particular  quot answer quot  to this problem was not listed in any of the above answers

User · Answer

In a one to many and many to one relationship this error will occur  If you attempt to devote same instance from many to one entity to more than one instance from one to many entity  For example  each person can have many books but each of these books can be owned by only one person if you consider more than one owner for a book this issue is raised

User · Answer

Explanation on practice  If you try to save your object  e g    Set lt Folder gt  folders   message getFolders       folders remove inputFolder      folders add trashFolder      message setFiles folders   MESSAGESDAO getMessageDAO   save message     you don t need to set updated object to a parent object   message setFiles folders     Simple save your parent object like   Set lt Folder gt  folders   message getFolders       folders remove inputFolder      folders add trashFolder         Not set updated object here MESSAGESDAO getMessageDAO   save message

User · Answer

I had the same problem  In my case  the issue was that someone used BeanUtils to copy the properties of one entity to another  so we ended up having two entities referencing the same collection   Given that I spent some time investigating this issue  I would recommend the following checklist    Look for scenarios like entity1 setCollection entity2 getCollection    and getCollection returns the internal reference to the collection  if getCollection   returns a new instance of the collection  then you don t need to worry   Look if clone   has been implemented correctly  Look for BeanUtils copyProperties entity1  entity2

User · Answer

In my case  I was copying and pasting code from my other classes  so I did not notice that the getter code was bad written    OneToMany fetch   FetchType LAZY  mappedBy    credito   public Set getConceptoses         return this letrases     public void setConceptoses Set conceptoses        this conceptoses   conceptoses      All references conceptoses but if you look at the get says letrases

User · Answer

Hibernate shows this error when you attempt to persist more than one entity instance sharing the same collection reference  i e  the collection identity in contrast with collection equality    Note that it means the same collection  not collection element - in other words relatedPersons on both person and anotherPerson must be the same  Perhaps you re resetting that collection after entities are loaded  Or you ve initialized both references with the same collection instance

User · Answer

Reading online the cause of this error can be also an hibernate bug  as workaround that it seems to work  it is to put a   session clear     You must to put the clear after getting data and before commit and close  see example     getting data SrReq sr    SrReq  crit uniqueResult    SrSalesDetailDTO dt SrSalesDetailMapper INSTANCE map sr     CLEAR             session clear      close session session getTransaction   commit    session close    return dt    I use this solution for select to database  for update or insert i don t know if this solution can work or can cause problems   My problem is equal at 100  of this  http   www progtown com topic128073-hibernate-many-to-many-on-two-tables html

User · Answer

I faced similar exception in my application  After looking into the stacktrace it was clear that exception was thrown within a FlushEntityEventListener class   In Hibernate 4 3 7 the MSLocalSessionFactory bean no longer supports the eventListeners property  Hence  one has to explicitly fetch the service registry from individual Hibernate session beans and then set the required custom event listeners   In the process of adding custom event listeners we need to make sure the corresponding default event listeners are removed from the respective Hibernate session   If the default event listener is not removed then the case arises of two event listeners registered against same event  In this case while iterating over these listeners  against first listeners any collections in the session will be flagged as reached and while processing the same collection against second listener would throw this Hibernate exception   So  make sure that when registering custom listeners corresponding default listeners are removed from registry

User · Answer

My problem was that I had setup an  ManyToOne relationship  Maybe if the answers above don t fix your problem you might want to check the relationship that was mentioned in the error message

User · Answer

I have experienced a great example of reproducing such a problem  Maybe my experience will help someone one day  Short version Check that your  Embedded Id of container has no possible collisions  Long version When Hibernate instantiates collection wrapper  it searches for already instantiated collection by CollectionKey in internal Map  For Entity with  Embedded id  CollectionKey wraps EmbeddedComponentType and uses  Embedded Id properties for equality checks and hashCode calculation  So if you have two entities with equal  Embedded Ids  Hibernate will instantiate and put new collection by the first key and will find same collection for the second key  So two entities with same  Embedded Id will be populated with same collection  Example Suppose you have Account entity which has lazy set of loans  And Account has  Embedded Id consists of several parts columns    Entity  Table schema    quot SOME quot   name    quot ACCOUNT quot   public class Account        OneToMany fetch   FetchType LAZY  mappedBy    quot account quot       private Set lt Loan gt  loans        Embedded     private AccountId accountId               Embeddable public class AccountId        Column name    quot X quot       private Long x            Column name    quot BRANCH quot       private String branchId            Column name    quot Z quot       private String z              Then suppose that Account has additional property mapped by  Embedded Id but has relation to other entity Branch   ManyToOne fetch   FetchType EAGER   JoinColumn name    quot BRANCH quot    MapsId  quot accountId branchId quot    NotFound action   NotFoundAction IGNORE   Look at this  private Branch branch   It could happen that you have no FK for Account to Brunch relation id DB so Account BRANCH column can have any value not presented in Branch table  According to  NotFound action   NotFoundAction IGNORE  if value is not present in related table  Hibernate will load null value for the property  If X and Y columns of two Accounts are same which is fine   but BRANCH is different and not presented in Branch table  hibernate will load null for both and Embedded Ids will be equal  So two CollectionKey objects will be equal and will have same hashCode for different Accounts  result    CollectionKey 34809   quot CollectionKey Account loans Account 43deab74  quot   role    quot Account loans quot   key    Account 26451    keyType    EmbeddedComponentType 21355    factory    SessionFactoryImpl 21356    hashCode   1187125168  entityMode    EntityMode 17415   quot pojo quot   result    CollectionKey 35653   quot CollectionKey Account loans Account 33470aa  quot   role    quot Account loans quot   key    Account 35225    keyType    EmbeddedComponentType 21355    factory    SessionFactoryImpl 21356    hashCode   1187125168  entityMode    EntityMode 17415   quot pojo quot   Because of this  Hibernate will load same PesistentSet for two entities

[java] Found shared references to a collection org.hibernate.HibernateException

Examples related to java

Examples related to hibernate

Examples related to grails

Examples related to groovy

Examples related to gorm