LazyInitializationException in Spring Boot JPA - How to fix?

Question

I'm getting this error when trying to access a collection after fetching an entity:

```
org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: com.example.User.posts, could not initialize proxy - no Session
```

My entities:
```java
@Entity
public class User {
    @OneToMany(mappedBy = "user")
    private List posts;
}
```

I understand it's because the session is closed, but what's the best way to fix this in Spring Boot?

java_master · Accepted Answer

There are several ways to fix LazyInitializationException. Here are the best approaches:

**Solution 1: Use DTOs with JOIN FETCH (Recommended)**
```java
@Query("SELECT u FROM User u LEFT JOIN FETCH u.posts WHERE u.id = :id")
User findUserWithPosts(@Param("id") Long id);
```

**Solution 2: Use @EntityGraph**
```java
@Entity
@NamedEntityGraph(
    name = "User.posts",
    attributeNodes = @NamedAttributeNode("posts")
)
public class User { }

// In repository:
@EntityGraph(value = "User.posts", type = EntityGraph.EntityGraphType.LOAD)
Optional findWithPostsById(Long id);
```

**Solution 3: Use Open Session in View (NOT recommended for production)**
```yaml
spring:
  jpa:
    open-in-view: true  # Default, but disable in production
```

**Solution 4: Use DTO Projection (Best for APIs)**
```java
public interface UserDTO {
    String getName();
    String getEmail();
    List getPosts();
}

@Query("SELECT u.name as name, u.email as email FROM User u WHERE u.id = :id")
UserDTO findUserDTOById(@Param("id") Long id);
```

**Solution 5: Change to EAGER (Generally NOT recommended)**
```java
@OneToMany(mappedBy = "user", fetch = FetchType.EAGER)
private List posts;  // Can cause performance issues
```

**Recommendation:**
- Use JOIN FETCH for web transactions
- Use DTO projections for API responses
- Disable `open-in-view` in production
- Never use EAGER fetching on collections

1 Answer