LazyInitializationException Within a @Transactional Method

Question

I am running into the org.hibernate.LazyInitializationException error when I try to access a lazy loaded exception when excecuting the following:

@Transactional
public void displayAddresses()
{
     Person person = getPersonByID(1234);
     List<Address> addresses = person.getAddresses(); // Exception Thrown Here

     for(Address address : addresses)
          System.out.println(address.getFullAddress());
}

My entities look like this:

@Entity
@Table("PERSON_TBL")
public class Person
{
     ...

     @OneToMany(cascade=CascadeType.ALL, targetEntity=Address.class, mappedBy="person")
     private List<Address> addresses;

     ...
}

@Entity
@Table("ADDRESS_TBL")
public class Address
{
     ...

     @ManyToOne(targetEntity=Person.class)
     @JoinColumn(name="PERSON_ID", referencedColumnName="PERSON_ID")
     Person person;

     ...
}

I was under the impression that by using the @Transactional annotation in my displayAddresses() method, it would keep the session alive until the method was completed, allowing me to access the lazy-loaded Address collection.

Am I missing something?

EDIT

In accordance with Tomasz's advice: Within my displayAddresses() method, the status of TransactionSynchronizationManager.isActualTransactionActive(), turned out to be false.

That does narrow down the problem, but why would my Transaction not be active at this point?

Can you call TransactionSynchronizationManager.isActualTransactionActive()? It should return true. Otherwise @Transasctional is not working. — Tomasz Nurkiewicz
– Tomasz Nurkiewicz, Commented Feb 16, 2012 at 20:01
@TomaszNurkiewicz I edited my original post to include more information based on your suggestion. — Tyler Murry
– Tyler Murry, Commented Feb 16, 2012 at 20:12
Do you have <tx:annotation-driven/> in your configuration? Is your displayAddresses() method in a Spring-managed bean? Do you call this method from outside or from other transactional method? — Tomasz Nurkiewicz
– Tomasz Nurkiewicz, Commented Feb 16, 2012 at 20:15
How do you invoke the displayAddresses() method - from a method of the same bean? — Ralph
– Ralph, Commented Feb 16, 2012 at 21:26

machinery · Accepted Answer · 2014-03-10 08:49:39Z

5

This is already answered, but just wanted to post an alternative answer which worked for me in a similar case - for future generations ;)

In my case the issue was caused by the fact that the instance which contained the lazy-loaded collection had been manually evicted (all within transaction boundaries).

answered Mar 10, 2014 at 8:49

machinery

3,9454 gold badges43 silver badges53 bronze badges

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

1 Comment

Kamil Bęben Over a year ago

It wasn't like that in my case, but it got me thinking - and it turned out that at one point an entity was cached (using ehcache) instead of dto - make sure that you are not doing it either

Tyler Murry · Accepted Answer · 2012-02-17 14:08:41Z

0

Having <tx:annotation-driven /> in my configuration file and using a Spring-managed version of my service class (to call the displayAddresses() method) did the trick.

answered Feb 17, 2012 at 14:08

Tyler Murry

2,8453 gold badges31 silver badges49 bronze badges

Collectives™ on Stack Overflow

LazyInitializationException Within a @Transactional Method

2 Answers 2

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related