如何解决“惰性初始化角色集合失败”Hibernate异常

我有这样一个问题:

org.hibernate.LazyInitializationException:惰性初始化role: mvc3.model.Topic.comments集合失败，没有会话或会话已关闭

下面是模型:

@Entity
@Table(name = "T_TOPIC")
public class Topic {

    @Id
    @GeneratedValue(strategy=GenerationType.AUTO)
    private int id;

    @ManyToOne
    @JoinColumn(name="USER_ID")
    private User author;

    @Enumerated(EnumType.STRING)    
    private Tag topicTag;

    private String name;
    private String text;

    @OneToMany(mappedBy = "topic", cascade = CascadeType.ALL)
    private Collection<Comment> comments = new LinkedHashSet<Comment>();

    ...

    public Collection<Comment> getComments() {
           return comments;
    }

}

调用model的控制器如下所示:

@Controller
@RequestMapping(value = "/topic")
public class TopicController {

    @Autowired
    private TopicService service;

    private static final Logger logger = LoggerFactory.getLogger(TopicController.class);


    @RequestMapping(value = "/details/{topicId}", method = RequestMethod.GET)
    public ModelAndView details(@PathVariable(value="topicId") int id)
    {

            Topic topicById = service.findTopicByID(id);
            Collection<Comment> commentList = topicById.getComments();

            Hashtable modelData = new Hashtable();
            modelData.put("topic", topicById);
            modelData.put("commentList", commentList);

            return new ModelAndView("/topic/details", modelData);

     }

}

jsp页面看起来如下所示:

<%@page import="com.epam.mvc3.helpers.Utils"%>
<%@ page language="java" contentType="text/html; charset=UTF-8" pageEncoding="UTF-8"%>
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<%@ page session="false" %>
<html>
<head>
      <title>View Topic</title>
</head>
<body>

<ul>
<c:forEach items="${commentList}" var="item">
<jsp:useBean id="item" type="mvc3.model.Comment"/>
<li>${item.getText()}</li>

</c:forEach>
</ul>
</body>
</html>

在查看jsp时，将引发异常。在c:forEach循环的行中

当前回答

为了延迟加载集合，必须有一个活动会话。在web应用中，有两种方法可以做到这一点。您可以使用Open Session In View模式，其中使用拦截器在请求开始时打开会话，并在结束时关闭会话。风险在于你必须有可靠的异常处理，否则你可能会绑定所有的会话，你的应用程序可能会挂起。

The other way to handle this is to collect all the data you need in your controller, close your session, and then stuff the data into your model. I personally prefer this approach, as it seems a little closer to the spirit of the MVC pattern. Also if you get an error from the database this way you can handle it a lot better than if it happens in your view renderer. Your friend in this scenario is Hibernate.initialize(myTopic.getComments()). You will also have to reattach the object to the session, since you're creating a new transaction with every request. Use session.lock(myTopic,LockMode.NONE) for that.

2012-07-31 20:13:23

其他回答

对于这个惰性初始化问题有多种解决方案

1)将关联Fetch类型从LAZY更改为EAGER，但这不是一个好的做法，因为这会降低性能。

2)使用FetchType。在关联对象上使用LAZY，并在您的服务层方法中使用Transactional注释，以便会话保持打开状态，并且当您调用topicById.getComments()时，子对象(注释)将被加载。

3)另外，在控制器层请尽量使用DTO对象而不是实体。在你的例子中，会话在控制器层被关闭。所以最好在服务层将实体转换为DTO。

2020-04-02 09:24:57

此问题是由于在关闭hibernate会话的情况下访问属性造成的。控制器中没有hibernate事务。

可能的解决方式:

Do all this logic, in the service layer, (with the @Transactional), not in the controller. There should be the right place to do this, it is part of the logic of the app, not in the controller (in this case, an interface to load the model). All the operations in the service layer should be transactional. i.e.: Move this line to the TopicService.findTopicByID method: Collection commentList = topicById.getComments(); Use 'eager' instead of 'lazy'. Now you are not using 'lazy' .. it is not a real solution, if you want to use lazy, works like a temporary (very temporary) workaround. use @Transactional in the Controller. It should not be used here, you are mixing service layer with presentation, it is not a good design. use OpenSessionInViewFilter, many disadvantages reported, possible instability.

一般来说，最佳解是1。

2017-02-13 14:17:16

这是一个老问题，但下面的信息可以帮助人们寻找答案。

@VladMihalcea的回答很有用。你不能依赖FetchType。相反，您应该在需要时将注释加载到Topic实体中。

如果您没有显式地定义您的查询以便您可以指定连接获取，那么使用@NamedEntityGraph和@EntityGraph您可以覆盖FetchType。LAZY(默认情况下@OneToMany关联使用LAZY)在运行时加载注释，只在需要时加载Topic。这意味着您将注释的加载限制在那些真正需要注释的方法(查询)上。JPA定义的实体图:

实体图可以与find方法一起使用，也可以作为查询提示覆盖或增强FetchType语义。

您可以基于这里的JPA示例使用它。或者，如果您使用Spring Data JPA，那么您可以基于Spring提供的示例来使用它。

2021-04-01 13:34:04

原因是你试图在关闭服务内的会话后在你的控制器上获得commentList。