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

If y'all are working inwards Hibernate framework, in addition to then y'all know that 1 of the telephone substitution characteristic of Hibernate is "lazy initialization", which allows framework to lazily initialize dependencies, human relationship or association lazily from database on withdraw basis. For example, if y'all are dealing amongst User object, which has human relationship amongst Permission object similar 1 user tin rank the axe own got multiple permissions, in addition to then Hibernate may pick out non to initialize the collection which holds all permissions at the fourth dimension it initialized User object in addition to instead returns a proxy object. At this point, if y'all unopen your session in addition to missive of the alphabet tries to access an attribute from Permission object, y'all volition teach "org.hibernate.LazyInitializationException: could non initialize proxy - no Session inwards Hibernate".

Why this fault comes, because hibernate needs to teach database to initialize the proxy object, in addition to connectedness is already closed. If y'all remember, what nosotros discussed inwards difference betwixt teach vs charge inwards hibernate that Proxy object is exclusively initialized inwards Hibernate if y'all access whatever attribute other than id itself, that's why y'all would exclusively encounter LazyInitializationException if y'all attempt to access an attribute other than id.

In this article, nosotros volition encounter dissimilar scenarios on which y'all could mayhap teach "org.hibernate.LazyInitializationException: could non initialize proxy - no Session inwards Hibernate" in addition to how to solve them appropriately.

I own got tried to explicate reasons which caused the error, in addition to explained the solution equally why it volition work, only if y'all nevertheless confront issues, in addition to then experience costless to post service it here.

By the way, expert agreement of lazy initialization is too a good Hibernate interview question, therefore this non exclusively aid y'all to solve this fault only too to produce good during interviews.

1) Code tries to access a lazy initialized holding or collection in addition to session is non available.

This is yesteryear far most mutual argue of "LazyInitializationException: could non initialize proxy". In gild to honour the argue y'all withdraw to await your code carefully. Here is 1 instance to understand, how lazy initialization exception comes inwards 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 constituent = roles.get(0); //  This work volition throw error

Exception inwards 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 inwards hibernate mapping file.

Advantage in addition to Disadvantages of lazy=false inwards Hibernate
Collection classes are big listing of other objects, which are non e'er accessed.

Better Solution :
The existent work is that y'all are trying to access a collection inwards an object that is detached or associated session is closed. You withdraw to re-attach the object earlier accessing the collection to the electrical flow session. You tin rank the axe either reattach the object yesteryear calling session.update(object); Or y'all tin rank the axe movement the code which access proxy object to the work earlier y'all unopen the session.

In short, though making lazy=false is unproblematic in addition to certain brusk way to solve "Exception inwards thread "main" org.hibernate.LazyInitializationException: could non initialize proxy - no Session" it is non a expert solution because y'all are throwing away the Lazy Initialization characteristic of hibernate. When lazy=false, the collection is loaded inwards retention at the same fourth dimension that the object is requested. This agency that if nosotros own got a collection amongst M items, they all volition live loaded inwards memory, despite nosotros are going to access them or not. This tin rank the axe upshot inwards to a greater extent than retention consumption in addition to tedious initialization of object amongst lot of association or dependency.

2) Upgrading from Hibernate 2.1 to Hibernate 3.0

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

Context : You may encounter "org.hibernate.LazyInitializationException: could non initialize proxy - no Session" spell upgrading from hibernate 2.1 to hibernate 3.0. You volition all of a abrupt honour yourself puzzling what happened, it was working earlier update. Reasons is, Hibernate three introduced lazy loading equally the default i.e. lazy="true". If y'all desire it to move the same equally earlier y'all tin rank the axe grade everything as lazy="false". Alternatively you'll own got to start eagerly initialising your entities in addition to associations.

3) Hibernate amongst JPA Annotation

If y'all are using hibernate amongst JPA annotations in addition to manually managing your transactions, in addition to then y'all tin rank the axe too attempt this equally good to bargain with LazyInitializationException inwards Hibernate . In your service cast in that place should live a setter for entity director amongst @PersistenceContext. modify this to @PersistenceContext(type = PersistenceContextType.EXTENDED). Then y'all tin rank the axe access lazy holding inwards whatever where. By the way, its worth recall 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 fix Exception inwards thread "main" org.hibernate.LazyInitializationException: could non initialize proxy - no Session. We own got seen that this fault mainly comes when y'all own got closed the connectedness in addition to trying to access the proxy object which is no fully initialized. Since Proxy object needs a connection, y'all tin rank the axe 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 exercise due to surgical physical care for argue only tin rank the axe live used during prototyping, testing, in addition to demo. Don't surprise if y'all start fourth dimension sees this fault when upgrading from Hibernate 2.1 to 3.0, because that's the version when Hibernate made lazy initialization enabled yesteryear default. If y'all own got faced this fault inwards whatever other scenario or trying to solve "org.hibernate.LazyInitializationException: could non initialize proxy - no Session", y'all tin rank the axe too post service your fault in addition to code hither in addition to nosotros tin rank the axe own got a await together.

Further Learning
answer)

Difference betwixt get() in addition to load() method inwards Hibernate? (answer)

5 Spring in addition to Hibernate Training Courses for Java developers (list)

2 Books to Learn Hibernate inwards 2017 (books)

5 Books to Learn Spring Framework inwards 2017 (books)

Why Hibernate Entity cast should non live lastly inwards Java? (answer)

10 Hibernate Questions from Java Interviews (list)

Thanks for reading this article, if y'all similar this article in addition to interview inquiry in addition to then delight part amongst your friends in addition to colleagues. If y'all own got whatever inquiry or feedback in addition to then delight driblet a comment.