Hibernate - A collection with cascade all-delete-orphan was no longer referenced by the owning entity instance

Question

I m having the following issue when trying to update my entity    A collection with cascade    all-delete-orphan    was no longer referenced by the owning entity instance     I have a parent entity and it has a Set lt     gt  of some children entities  When I try to update it  I get all the references to be set to this collections and set it   The following code represents my mapping    OneToMany mappedBy    parentEntity   fetch   FetchType EAGER   Cascade   CascadeType ALL  CascadeType DELETE ORPHAN    public Set lt ChildEntity gt  getChildren         return this children      I ve tried to clean the Set lt     only  according to this  How to  possible  solve the problem but it didn t work   If you have any ideas  please let me know   Thanks

User · Answer

Mine was completely different with Spring Boot! For me it was not due to setting collection property.

In my tests I was trying to create an entity and was getting this error for another collection that was unused!

After so much trying I just added a @Transactional on the test method and it solved it. Don't no the reason though.

User · Answer

I am using Spring Boot and had this issue with a collection  in spite of not directly overwriting it  because I am declaring an extra field for the same collection with a custom serializer and deserializer in order to provide a more frontend-friendly representation of the data     public List lt Attribute gt  getAttributes         return attributes         public void setAttributes List lt Attribute gt  attributes        this attributes   attributes          JsonSerialize using   AttributeSerializer class    public List lt Attribute gt  getAttributesList         return attributes          JsonDeserialize using   AttributeDeserializer class    public void setAttributesList List lt Attribute gt  attributes        this attributes   attributes        It seems that even though I am not overwriting the collection myself  the deserialization does it under the hood  triggering this issue all the same  The solution was to change the setter associated with the deserializer so that it would clear the list and add everything  rather than overwrite it      JsonDeserialize using   AttributeDeserializer class    public void setAttributesList List lt Attribute gt  attributes        this attributes clear        this attributes addAll attributes

User · Answer

The only time I get this error is when I try to pass NULL into the setter for the collection   To prevent this  my setters look like this   public void setSubmittedForms Set lt SubmittedFormEntity gt  submittedForms        if submittedForms    null            this submittedForms clear              else           this submittedForms   submittedForms

User · Answer

This is in contrast to the previous answers  I had exactly the same error   A collection with cascade    all-delete-orphan    was no longer referenced      when my setter function looked like this   public void setTaxCalculationRules Set lt TaxCalculationRule gt  taxCalculationRules         if  this taxCalculationRules    null             this taxCalculationRules   taxCalculationRules         else           this taxCalculationRules retainAll taxCalculationRules            this taxCalculationRules addAll taxCalculationRules              And then it disappeared when I changed it to the simple version   public void setTaxCalculationRules Set lt TaxCalculationRule gt  taxCalculationRules         this taxCalculationRules   taxCalculationRules        hibernate versions - tried both 5 4 10 and 4 3 11  Spent several days trying all sorts of solutions before coming back to the simple assignment in the setter  Confused now as to why this so

User · Answer

be careful with   BeanUtils copyProperties newInsum  insumOld  code      This method too break the hibernate

User · Answer

When I read in various places that hibernate didn t like you to assign to a collection  I assumed that the safest thing to do would obviously be to make it final like this   class User     private final Set lt Role gt  roles   new HashSet lt  gt      public void setRoles Set lt Role gt  roles      this roles retainAll roles     this roles addAll roles         However  this doesn t work  and you get the dreaded  no longer referenced  error  which is actually quite misleading in this case   It turns out that hibernate calls your setRoles method AND it wants its special collection class installed here  and won t accept your collection class  This had me stumped for a LONG time  despite reading all the warnings about not assigning to your collection in your set method   So I changed to this   public class User     private Set lt Role gt  roles   null     public void setRoles Set lt Role gt  roles      if  this roles    null        this roles   roles      else       this roles retainAll roles      this roles addAll roles             So that on the first call  hibernate installs its special class  and on subsequent calls you can use the method yourself without wrecking everything  If you want to use your class as a bean  you probably need a working setter  and this at least seems to work

User · Answer

I was getting A collection with cascade    all-delete-orphan    was no longer referenced by the owning entity instance when I was setting parent setChildren new ArrayList lt  gt      When I changed to parent getChildren   clear    it solved the problem   Check for more details  HibernateException - A collection with cascade  all-delete-orphan  was no longer referenced by the owning entity instance

User · Answer

In my case it was concurrent access to one Hibernate Session from several threads  I had the Spring Boot Batch and RepositoryItemReader implementation where I fetched entities by page request with size 10  For example my entities are   Entity class JobEntity        ManyToOne fetch   FetchType LAZY      private GroupEntity group      Entity class GroupEntity        OneToMany mappedBy    quot group quot   cascade   CascadeType ALL  fetch   FetchType LAZY  orphanRemoval   true      private Set lt Config gt  configs      Batch process  reader - gt  processor - gt  writer in one transaction  In that entities configuration  GroupEntity can escapes to other threads  First thread that entered to read section fetches the page of JobEntity with size 10  RepositoryItemReader doRead   this items contain one shared GroupEntity object  because all of them pointed to the same group id   Then it takes the first entity  Next threads that come to read section take JobEntity from this page one by one  until this page will be exhausted  So now threads have access to the same GroupEntity instance thought the JobEntity instances  that is unsafe multi thread access to the one Hibernate Session

User · Answer

I had the same issue  but it was when the set was null  Only in the Set collection  in List work fine  You can try to the hibernate annotation  LazyCollection LazyCollectionOption FALSE  instead of JPA annotation fetch   FetchType EAGER  My solution  This is my configuration and work fine  OneToMany mappedBy    quot format quot   cascade   CascadeType ALL  orphanRemoval   true   LazyCollection LazyCollectionOption FALSE  private Set lt Barcode gt  barcodes    OneToMany mappedBy    quot format quot   cascade   CascadeType ALL  orphanRemoval   true   LazyCollection LazyCollectionOption FALSE  private List lt FormatAdditional gt  additionals

User · Answer

There is this bug which looks suspiciously similar  https   hibernate atlassian net browse HHH-9940  And the code to reproduce it  https   github com abenneke sandbox tree master hibernate-null-collection src test There are 2 possible fixes to this   the collection is initialized with an empty collection  instead of null   orphanRemoval is set to false   Example - was   OneToMany cascade   CascadeType REMOVE          mappedBy    quot jobEntity quot   orphanRemoval   true  private List lt JobExecutionEntity gt  jobExecutionEntities   became   OneToMany cascade   CascadeType REMOVE          mappedBy    quot jobEntity quot   private List lt JobExecutionEntity gt  jobExecutionEntities

User · Answer

I had the same error  The problem for me was  that after saving the entity the mapped collection was still null and when trying to update the entity the exception was thrown  What helped for me  Saving the entity  then make a refresh  collection is no longer null  and then perform the update  Maybe initializing the collection with new ArrayList   or something might help as well

User · Answer

All those answers didnt help me  BUT I found another solution  I had an Entity A containing a List of Entity B  Entity B contained a List of Entity C  I was trying to update Entity A and B  It worked  But when updating Entity C  I got the mentioned error  In entity B I had an annotation like this   OneToMany mappedBy    quot entity b quot   cascade    CascadeType ALL    orphanRemoval   true  var c  List lt EntityC gt     I simply removed orphanRemoval and the update worked

User · Answer

Had this issue with spring-boot 2 4 1 when running the tests in bulk from  Intellij Idea  version 2020 3  The issue doesn t appear when running only one test at a time from IntelliJ or when running the tests from command line  Maybe Intellij caching problem  Follow up  The problem appears when running tests using the maven-surefire-plugin reuseForks true  Using reuseForks false would provide a quick fix  but the tests running time will increase dramatically  Because we are reusing forks  the database context might become dirty due to other tests that are run - without cleaning the database context afterwards  The obvious solution would be to clean the database context before running a test  but the best one should be to clean up the database context after each test  solving the root cause of the original problem   Using the  Transactional annotation on your test methods will guarantee that your database changes are rolled back at the end of the test methods  See the Spring documentation on transactions  https   docs spring io spring-framework docs current reference html testing html testcontext-tx

User · Answer

Check all of the places where you are assigning something to sonEntities   The link you referenced distinctly points out creating a new HashSet but you can have this error anytime you reassign the set   For example   public void setChildren Set lt SonEntity gt  aSet        this sonEntities   aSet    This will override the set that Hibernate is tracking      Usually you want to only  new  the set once in a constructor   Any time you want to add or delete something to the list you have to modify the contents of the list instead of assigning a new list   To add children   public void addChild SonEntity aSon        this sonEntities add aSon       To remove children   public void removeChild SonEntity aSon        this sonEntities remove aSon

User · Answer

Following solution worked for me    Parent class  OneToMany mappedBy    parent               cascade  CascadeType ALL  orphanRemoval   true   OrderBy value  ordinal ASC   List lt Child gt  children   new ArrayList lt  gt       Updated setter of children  public void setChildren List lt Children gt  children        this children addAll children       for  Children child  children          child setParent this         Child class  ManyToOne  JoinColumn name  Parent ID   private Parent parent

User · Answer

Actually  my problem was about equals and hashcode of my entities  A legacy code can bring a lot of problems  never forget to check it out  All I ve done was just keep delete-orphan strategy and correct equals and hashcode

User · Answer

I used  user2709454 approach with small improvement   public class User       private Set lt Role gt  roles       public void setRoles Set lt Role gt  roles            if  this roles    null                this roles   roles            else if this roles    roles       not the same instance  in other case we can get ConcurrentModificationException from hibernate AbstractPersistentCollection             this roles clear                if roles    null                   this roles addAll roles

User · Answer

HAS RELATION TYPE     Don t try to instantiate the collection when it s declared in hasMany  just add and remove objects    class Parent       static hasMany    childs Child        USE RELATION TYPE     But the collection could be null only when is declared as a property  use relation  and is not initialized in declaration   class Parent       List lt Child gt  childs

User · Answer

Instead of assigning new collection  public void setChildren Set lt ChildEntity gt  children        this children   children      Replace all elements with  public void setChildren Set lt ChildEntity gt  children        Collections replaceAll this children children

User · Answer

One other cause may be using lombok    Builder - causes to save Collections emptyList   even if you say  myCollection new ArrayList       Singular - ignores the class level defaults and leaves field null even if the class field was declared as myCollection   new ArrayList    My 2 cents  just spent 2 hours with the same

User · Answer

The method   public void setChildren Set lt SonEntity gt  aSet        this sonEntities   aSet      works if the parentEntity is detached and again if we update it  But if the entity is not detached from per context   i e  find and update operations are in the same transaction  the below method works   public void setChildren Set lt SonEntity gt  aSet          this sonEntities   aSet    This will override the set that Hibernate is tracking      this sonEntities clear        if  aSet    null            this sonEntities addAll aSet

User · Answer

Adding my dumb answer   We re using Spring Data Rest  This was our pretty standard relationship   The pattern was used elsewhere      Parent class  OneToMany mappedBy    parent               cascade  CascadeType ALL  orphanRemoval   true   LazyCollection LazyCollectionOption FALSE  List lt Child gt  children   new LinkedList lt  gt        Child class  ManyToOne fetch   FetchType LAZY   JoinColumn name    ParentID   updatable   false   JsonBackReference Parent parent   With the relationship we created  it was always intended that the children would be added through their own repo   I had not yet added the repo   The integration test we had was going through a complete lifecycle of the entity via REST calls so the transactions would close between requests   No repo for the child meant the json had the children as part of the main structure instead of in  embedded   Updates to the parent would then cause problems

User · Answer

I had this problem when trying to use TreeSet  I did initialize oneToMany with TreeSet which works   OneToMany mappedBy    question   fetch   FetchType EAGER  cascade     CascadeType ALL    orphanRemoval true   OrderBy  id   private Set lt WizardAnswer gt  answers   new TreeSet lt WizardAnswer gt       But  this will bring the error described at the question above  So it seems that hibernate supported SortedSet and if one just change the line above to   OneToMany mappedBy    question   fetch   FetchType EAGER  cascade     CascadeType ALL    orphanRemoval true   OrderBy  id   private SortedSet lt WizardAnswer gt  answers    it works like magic    more info on hibernate SortedSet can be here

User · Answer

It might be caused by hibernate-enhance-maven-plugin  When I enabled enableLazyInitialization property this exception started on happening on my lazy collection  I m using hibernate 5 2 17 Final   Note this two hibernate issues    https   hibernate atlassian net browse HHH-10708 https   hibernate atlassian net browse HHH-11459

User · Answer

I ran into this when updating an entity with a JSON post request  The error occurred when I updated the entity without data about the children  even when there were none   Adding   children         to the request body solved the problem

User · Answer

OneToMany mappedBy    parent   cascade  CascadeType ALL  orphanRemoval   true  List lt Child gt  children   new ArrayList lt  gt       I experienced the same error when I was adding child object to the existing list of Child Objects   childService saveOrUpdate child   parent addToChildren child   parentService saveOrUpdate parent     What resolved my problem is changing to   child   childService saveOrUpdate child     Now the child is revive with other details as well and it worked fine

[java] Hibernate - A collection with cascade=”all-delete-orphan” was no longer referenced by the owning entity instance

Examples related to java

Examples related to hibernate

Examples related to hibernate-mapping