Solved

Illegal attempt to associate a collection with two open sessions

Posted on 2014-01-27
6
3,172 Views
Last Modified: 2014-01-29
Hello there,

I am trying to update a record in one of the frames in my application and I get this error. Before it was working fine. I mean I could add and update the records in the frame. then I added the delete operation and the del is working but when I try to update I get this error. please help. I have attached my classes.

cheers
Zolf

org.hibernate.HibernateException: Illegal attempt to associate a collection with two open sessions
=== 2014-01-28 09:45:18,612 [l0-2] DEBUG RPCManager - Content type for RPC transaction: text/plain; charset=UTF-8
=== 2014-01-28 09:45:18,612 [l0-2] DEBUG RPCManager - DMI response, dropExtraFields: true
=== 2014-01-28 09:45:18,612 [l0-2] INFO  Compression - /kaizenerpweb/sc/IDACall: 144 -> 132 bytes
      at org.hibernate.collection.AbstractPersistentCollection.setCurrentSession(AbstractPersistentCollection.java:432)
      at org.hibernate.event.def.OnUpdateVisitor.processCollection(OnUpdateVisitor.java:66)
      at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:124)
      at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:84)
      at org.hibernate.event.def.AbstractVisitor.processEntityPropertyValues(AbstractVisitor.java:78)
      at org.hibernate.event.def.AbstractVisitor.process(AbstractVisitor.java:146)
      at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performUpdate(DefaultSaveOrUpdateEventListener.java:316)
      at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsDetached(DefaultSaveOrUpdateEventListener.java:246)
      at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:112)
      at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:93)
      at org.hibernate.impl.SessionImpl.fireSaveOrUpdate(SessionImpl.java:535)
      at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:527)
      at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:523)
      at com.kaizen.erp.server.bussinessLogic.supplier.SupplierOrderBussinessLogic.saveSupplierOrder(SupplierOrderBussinessLogic.java:134)
      at com.kaizen.erp.server.bussinessLogic.supplier.SupplierOrderBussinessLogic.add(SupplierOrderBussinessLogic.java:110)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
SupplierOrderBussinessLogic.java
SupplierOrder.hbm.xml
0
Comment
Question by:zolf
  • 3
  • 3
6 Comments
 
LVL 35

Expert Comment

by:mccarl
Comment Utility
Can you provide the code for your HibernateUtils class please?
0
 

Author Comment

by:zolf
Comment Utility
Hi mccarl,

I have attached the file you mentioned.

cheers
Zolf
HibernateUtills.java
0
 
LVL 35

Expert Comment

by:mccarl
Comment Utility
Ok, I believe this error is due to the "supplierOrder" object being retrieved in the "getSupplierOrderFromRequest" method (line 108) under one session and then attempting to saveOrUpdate the same object in the "saveSupplierOrder" method (line 110) under a new session. And since your session handling seems "a bit odd" and you are only closing sessions when "session.isConnected()" is false (and I'm guessing that generally it isn't false) that the first session is still open when you are trying to manipulate your object in the second session.

So some potential fixes are... properly closing the session regardless if it is still connected may work (although that may introduce other problems, it's hard to tell with your code a bit all over the place). Otherwise, try and only open the one session for the entire request, rather than having that "add" method where you call additional methods that each opens its own session.
0
Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 

Author Comment

by:zolf
Comment Utility
thanks for your comments. but It was working properly before when I added the one to many in the SupplierOrder.hbm.xml to be able to perform delete cascade, then this issue came up in the update process.
0
 
LVL 35

Accepted Solution

by:
mccarl earned 500 total points
Comment Utility
but It was working properly before
That may well be the case, but I don't know what the "before" code/configuration looked like, I only know what you have now. In fact, you have now given a little bit more information... In the original question, you just said that you "added the delete operation" which I took to meaning that you added the code for the delete method, but now you say that you had to actually add the mapping relationships as well. That may explain what has happened...

So, "before", you had incorrect session handling code but a simpler relationship mapping defined and so despite the incorrect session handling Hibernate was probably still able to carry on regardless. Now, you have added additional relationship mappings, it is just too much for Hibernate to work out what to do in the face of the incorrect session handling and so you get the Exception that you see.

I see you have two options... 1) Remove the delete operation and the changes you made to the mapping so that you are back to where you were and you can update records (probably not the best option because I'm guessing that you really want to be able to delete stuff) or 2) fix the session handling code (as described above) and be able to update and delete stuff (the ideal solution!!)
0
 

Author Comment

by:zolf
Comment Utility
also when I try to run a simple code like this too I get the error. I guess it has to do with this one to many which I added to my hbm.xml file

public static void main(String []args){
        SupplierOrder supplierOrder = getInstance().getSupplierOrderById(1L);
        if(supplierOrder!=null)
                getInstance().saveSupplierOrder(supplierOrder);
        else
                System.out.println("null");
}
0

Featured Post

How to improve team productivity

Quip adds documents, spreadsheets, and tasklists to your Slack experience
- Elevate ideas to Quip docs
- Share Quip docs in Slack
- Get notified of changes to your docs
- Available on iOS/Android/Desktop/Web
- Online/Offline

Join & Write a Comment

For beginner Java programmers or at least those new to the Eclipse IDE, the following tutorial will show some (four) ways in which you can import your Java projects to your Eclipse workbench. Introduction While learning Java can be done with…
Java contains several comparison operators (e.g., <, <=, >, >=, ==, !=) that allow you to compare primitive values. However, these operators cannot be used to compare the contents of objects. Interface Comparable is used to allow objects of a cl…
Viewers learn about the “while” loop and how to utilize it correctly in Java. Additionally, viewers begin exploring how to include conditional statements within a while loop and avoid an endless loop. Define While Loop: Basic Example: Explanatio…
Viewers will learn about the different types of variables in Java and how to declare them. Decide the type of variable desired: Put the keyword corresponding to the type of variable in front of the variable name: Use the equal sign to assign a v…

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now