LazyInitializationException - could not initialize proxy - no Session

Q: Use JOIN FETCH in your Repository query

When to use: Use this when you want to keep LAZY loading default but need the data for a specific API call.. JOIN FETCH tells Hibernate to fetch the related entity in the same SQL query, avoiding the need for a session later.

Q: Change fetch type to EAGER

When to use: Use this if you ALWAYS need the related data whenever you load the parent entity.. EAGER fetching tells Hibernate to load the relationship immediately. Warning: This can cause performance issues if overused.

Q: Map to a DTO inside @Transactional method

When to use: Use this if you want to return a DTO to the frontend instead of the Entity.. Perform the mapping from Entity to DTO inside a @Transactional service method while the session is still open.

🔴 The Error You're Seeing

Confirm this matches your console output. If it does, you're in the right place.

ERROR LOG

2023-10-25 10:15:30.812 ERROR 12345 --- [nio-8080-exec-1] o.a.c.c.C.[.[.[/].[dispatcherServlet]    : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed: org.hibernate.LazyInitializationException: could not initialize proxy [com.devinhyderabad.entity.User.department] - no Session] with root cause

org.hibernate.LazyInitializationException: could not initialize proxy [com.devinhyderabad.entity.User.department] - no Session

⚡ Quick Fix Works 80% of the time

Change the fetch type to EAGER or use JOIN FETCH in your repository query.

@Query("SELECT u FROM User u JOIN FETCH u.department")
List<User> findAllWithDepartment();

🛠️ Solutions (3 Ways to Fix)

Solution 1✓ Most common cause

Use JOIN FETCH in your Repository query

👉 Use this when you want to keep LAZY loading default but need the data for a specific API call.

JOIN FETCH tells Hibernate to fetch the related entity in the same SQL query, avoiding the need for a session later.

@Query("SELECT u FROM User u JOIN FETCH u.department")
List<User> findAllWithDepartment();

Solution 2

Change fetch type to EAGER

👉 Use this if you ALWAYS need the related data whenever you load the parent entity.

EAGER fetching tells Hibernate to load the relationship immediately. Warning: This can cause performance issues if overused.

@ManyToOne(fetch = FetchType.EAGER)
@JoinColumn(name = "department_id")
private Department department;

Solution 3

Map to a DTO inside @Transactional method

👉 Use this if you want to return a DTO to the frontend instead of the Entity.

Perform the mapping from Entity to DTO inside a @Transactional service method while the session is still open.

@Service
public class UserService {
    @Transactional
    public UserDTO getUser(Long id) {
        User user = repo.findById(id).get();
        return new UserDTO(user.getName(), user.getDepartment().getName());
    }
}

📋 Version Notes

Spring Boot 2.x

OpenSessionInView was true by default, masking this error in controllers.

Spring Boot 3.x

OpenSessionInView is false by default. The exception is thrown if accessed outside a session.

🧠 Why this Happens

Tap to expand the deep technical explanation

By default, @OneToMany and @ManyToMany relationships are LAZY. Hibernate doesn't fetch them from the database until you call the getter. If you call the getter AFTER the database session has closed (e.g., in your Controller or during JSON serialization), Hibernate throws this exception.

The HITEC City Parking Spot Analogy:

It's like borrowing a book from a library. You can only read it while the library is open. If you take it home (outside the session) and try to read a page (call a getter), you can't.

🛡️ How to Prevent This Next Time

Never return JPA Entities directly from your @RestController. Always map them to DTOs inside your @Service layer.