Hibernate JPA, Spring MVC and LazyInitializationException

Question

When trying to get items from db, I got this error:

13:00:13.876 [7838526@qtp-204712603-0] ERROR o.h.LazyInitializationException - failed to lazily initialize a collection of role: bo.myobj, no session or session was closed
org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: de.myob.linkedstuff, no session or session was closed

I understand that with switching to eager instead of lazy loading solves this problem, e.g.

@OneToMany(mappedBy = "myobj", cascade = CascadeType.ALL, fetch=FetchType.EAGER)

and I also understand that eager loading is discouraged. What is the best practitce in order to cope with this issue?

Sean Patrick Floyd · Accepted Answer · 2010-07-24 12:10:25Z

5

I am pretty sure this occurs when there is no active transaction.

Read the spring reference part about Declarative Transaction Management

Usually it boils down to your service method or class needing the @Transactional annotation if you use annotations or otherwise proper xml configuration of <tx:advice>.

answered Jul 24, 2010 at 12:10

Sean Patrick Floyd

301k72 gold badges481 silver badges598 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Ta Sas Over a year ago

Sorry, I have checked all beans - @Transactional is present in all DAO methods ... my xml looks fine too

Sean Patrick Floyd Over a year ago

Thanks for downvoting. What I meant is: are you still inside the transactional scope, when you access the collection? Because that's probably not happening inside a dao method, is it?

Jason Day · Accepted Answer · 2010-07-24 13:45:49Z

3

This is a common problem, usually caused by rendering the view after the hibernate Session is closed. A common solution is to use the Open Session In View pattern, which will keep the hibernate session open for the lifetime of the web request.

Spring comes with a filter that implements this pattern. To enable it for all JSP files in your application, for example, add something like this to your web.xml:

<filter>
    <filter-name>osivFilter</filter-name>
    <filter-class>org.springframework.orm.hibernate3.support.OpenSessionInViewFilter</filter-class>
</filter>

<filter-mapping>
    <filter-name>osivFilter</filter-name>
    <url-pattern>*.jsp</url-pattern>
</filter-mapping>

answered Jul 24, 2010 at 13:45

Jason Day

8,8391 gold badge43 silver badges46 bronze badges

1 Comment

Ta Sas Over a year ago

I inserted the lines, however, the laziiniterror persists :-(

Kwebble · Accepted Answer · 2010-07-24 15:30:39Z

2

Better separation between the persistence and other layers. Make sure the objects produced by the persistence layer do not include any reference to Hibernate.

The article Hibernate, Get Out of My POJO! may be helpful.

answered Jul 24, 2010 at 15:30

Kwebble

2,07514 silver badges23 bronze badges

2 Comments

Ta Sas Over a year ago

Thanks for the tip, I guess that is the right strategy. However, I have been running into so many issues since I have started using an ORM that I wonder if there is any benifit using any ORM ... sorry, just had to mention that :-(

Pascal Thivent Over a year ago

@erlord: Feel free to not use an ORM (at least not one with a defined persistence context) then :) And good luck!

Collectives™ on Stack Overflow

Hibernate JPA, Spring MVC and LazyInitializationException

3 Answers 3

2 Comments

1 Comment

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

1 Comment

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related