Dealing Amongst Org.Hibernate.Lazyinitializationexception: Could Non Initialize Proxy - No Session Inwards Hibernate Java

If yous are working inward Hibernate framework, thus yous know that 1 of the fundamental characteristic of Hibernate is "lazy initialization", which allows framework to lazily initialize dependencies, human relationship or association lazily from database on yell for basis. For example, if yous are dealing alongside User object, which has human relationship alongside Permission object similar 1 user tin lead maintain multiple permissions, thus Hibernate may select non to initialize the collection which holds all permissions at the fourth dimension it initialized User object together with instead returns a proxy object. At this point, if yous unopen your session together with missive of the alphabet tries to access an attribute from Permission object, yous volition teach "org.hibernate.LazyInitializationException: could non initialize proxy - no Session inward Hibernate".

Why this mistake comes, because hibernate needs to teach database to initialize the proxy object, together with connexion is already closed. If yous remember, what nosotros discussed inward difference betwixt teach vs charge inward hibernate that Proxy object is solely initialized inward Hibernate if yous access whatever attribute other than id itself, that's why yous would solely run across LazyInitializationException if yous endeavor to access an attribute other than id.

In this article, nosotros volition run across dissimilar scenarios on which yous could mayhap teach "org.hibernate.LazyInitializationException: could non initialize proxy - no Session inward Hibernate" together with how to solve them appropriately.

I lead maintain tried to explicate reasons which caused the error, together with explained the solution every bit why it volition work, only if yous withal confront issues, thus experience gratis to postal service it here.

By the way, skillful agreement of lazy initialization is too a good Hibernate interview question, thus this non solely assistance yous to solve this mistake only too to produce good during interviews.

1) Code tries to access a lazy initialized belongings or collection together with session is non available.

This is yesteryear far most mutual argue of "LazyInitializationException: could non initialize proxy". In enterprise to detect the argue yous yell for to expect your code carefully. Here is 1 instance to understand, how lazy initialization exception comes inward Hibernate :

Session s = sessions.openSession(); Transaction tx = s.beginTransaction();  Employee e = (Employee) s.createQuery("from Employee e where e.name=:empName").setString("empName", eName).uniqueResult(); List roles = u.getRoles();  tx.commit(); s.close();  String component subdivision = roles.get(0); //  This business volition throw error

Exception inward thread "main" org.hibernate.LazyInitializationException: could not initialize proxy - no Session    at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:57)    at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:111)    at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:150)

Easy Solution
Use lazy=false inward hibernate mapping file.

Advantage together with Disadvantages of lazy=false inward Hibernate
Collection classes are big listing of other objects, which are non ever accessed.

Better Solution :
The existent employment is that yous are trying to access a collection inward an object that is detached or associated session is closed. You yell for to re-attach the object earlier accessing the collection to the electrical flow session. You tin either reattach the object yesteryear calling session.update(object); Or yous tin motion the code which access proxy object to the business earlier yous unopen the session.

In short, though making lazy=false is uncomplicated together with certain brusque way to solve "Exception inward thread "main" org.hibernate.LazyInitializationException: could non initialize proxy - no Session" it is non a skillful solution because yous are throwing away the Lazy Initialization characteristic of hibernate. When lazy=false, the collection is loaded inward retentiveness at the same fourth dimension that the object is requested. This way that if nosotros lead maintain a collection alongside K items, they all volition survive loaded inward memory, despite nosotros are going to access them or not. This tin result inward to a greater extent than retentiveness consumption together with ho-hum initialization of object alongside lot of association or dependency.

2) Upgrading from Hibernate 2.1 to Hibernate 3.0

Cause : Hibernate 3.0 render lazy loading default every bit truthful i.e. lazy ="true"
Solution : In hibernate mapping file set lazy= "false"

Context : You may run across "org.hibernate.LazyInitializationException: could non initialize proxy - no Session" piece upgrading from hibernate 2.1 to hibernate 3.0. You volition all of a abrupt detect yourself puzzling what happened, it was working earlier update. Reasons is, Hibernate three introduced lazy loading every bit the default i.e. lazy="true". If yous desire it to function the same every bit earlier yous tin score everything as lazy="false". Alternatively you'll lead maintain to start eagerly initialising your entities together with associations.

3) Hibernate alongside JPA Annotation

If yous are using hibernate alongside JPA annotations together with manually managing your transactions, thus yous tin too endeavor this every bit good to bargain with LazyInitializationException inward Hibernate . In your service flat at that spot should survive a setter for entity director alongside @PersistenceContext. alter this to @PersistenceContext(type = PersistenceContextType.EXTENDED). Then yous tin access lazy belongings inward whatever where. By the way, its worth yell upward that, Spring EXTENDED persistence context type is for long conversation pattern, non the session-per-request pattern.

entity classes.

That's all almost how to create Exception inward thread "main" org.hibernate.LazyInitializationException: could non initialize proxy - no Session. We lead maintain seen that this mistake mainly comes when yous lead maintain closed the connexion together with trying to access the proxy object which is no fully initialized. Since Proxy object needs a connection, yous tin either reattach object to the session or carefully avoid writing such code, which access uninitialized Proxy object.

Another way to avoid LazyInitializationException is to disable lazy initialization characteristic of hibernate for your entity classes yesteryear using lazy="false" or disable it completely for your application yesteryear using default-lazy="false".

This solution is non recommended for production utilisation due to functioning argue only tin survive used during prototyping, testing, together with demo. Don't surprise if yous kickoff fourth dimension sees this mistake when upgrading from Hibernate 2.1 to 3.0, because that's the version when Hibernate made lazy initialization enabled yesteryear default. If yous lead maintain faced this mistake inward whatever other scenario or trying to solve "org.hibernate.LazyInitializationException: could non initialize proxy - no Session", yous tin too postal service your mistake together with code hither together with nosotros tin lead maintain a expect together.

Further Learning
answer)

Difference betwixt get() together with load() method inward Hibernate? (answer)

5 Spring together with Hibernate Training Courses for Java developers (list)

2 Books to Learn Hibernate inward 2017 (books)

5 Books to Learn Spring Framework inward 2017 (books)

Why Hibernate Entity flat should non survive terminal inward Java? (answer)

10 Hibernate Questions from Java Interviews (list)

Thanks for reading this article, if yous similar this article together with interview inquiry thus delight portion alongside your friends together with colleagues. If yous lead maintain whatever inquiry or feedback thus delight drib a comment.

Share this post