【发布时间】：2014-06-18 15:37:02
【问题描述】：
我收到一个我不明白的延迟初始化异常...
我使用 Java、Hibernate、Spring 和 Wicket。
所以，从表单的保存方法（扩展检票口表单）中，我在访问对象集合时得到一个 LazyInitializationException，但我可以立即访问具有相同“配置”的同一对象的另一个集合作为触发异常的集合：
这是表单中的代码：
therapyGroup.getTherapies().clear();
therapyGroup.getTherapies().addAll(therapiesOldGroup);
therapyGroup.getToxicities().add(lastTherapy.getToxicity());
这里是类中定义集合的部分：
@OneToMany(mappedBy = "therapyGroup", fetch = FetchType.LAZY, orphanRemoval=true)
@Cascade(value = { CascadeType.MERGE, CascadeType.PERSIST, CascadeType.DELETE, CascadeType.SAVE_UPDATE })
@OrderBy(value = "date asc")
@Filters( { @Filter(name = "deletedFilter", condition = "deleted <> :deletedParam") })
@Cache(usage = CacheConcurrencyStrategy.TRANSACTIONAL, region = "TherapyGroup")
@Lazy
public Set<Therapy> getTherapies() {
return therapies;
}
@OneToMany(mappedBy = "therapyGroup", fetch = FetchType.LAZY, orphanRemoval=true)
@Cascade(value = { CascadeType.MERGE, CascadeType.PERSIST, CascadeType.DELETE, CascadeType.SAVE_UPDATE })
@OrderBy(value = "date asc")
@Filters( { @Filter(name = "deletedFilter", condition = "deleted <> :deletedParam") })
@Cache(usage = CacheConcurrencyStrategy.TRANSACTIONAL, region = "TherapyGroup")
@Lazy
public Set<Toxicity> getToxicities() {
return toxicities;
}
“有问题的”集合是毒性集合。如果我先交换订单并调用毒性，它也会抛出LazyInitializationException。异常总是被毒性而不是疗法触发......为什么？
编辑：这是堆栈跟踪
根本原因：
org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: com.mycompany.myapp.data.TherapyGroup.toxicities, no session or session was closed
at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:383)
at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationExceptionIfNotConnected(AbstractPersistentCollection.java:375)
at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:368)
at org.hibernate.collection.PersistentSet.add(PersistentSet.java:212)
at com.mycompany.myapp.web.support.therapyend.TherapyEndSupportForm.onSaveFormData(TherapyEndSupportForm.java:135)
at com.mycompany.myapp.web.base.BaseForm.doSave(BaseForm.java:370)
at com.mycompany.myapp.web.base.BaseForm.saveAndTrigger(BaseForm.java:1137)
at com.mycompany.myapp.web.base.BaseForm.switchModalWindow(BaseForm.java:1128)
at com.mycompany.myapp.web.base.BaseForm.switchModalWindow(BaseForm.java:1077)
at com.mycompany.myapp.web.base.BaseForm.onSubmit(BaseForm.java:567)
at com.mycompany.myapp.web.comp.QuasiAjaxSubmitButton.onSubmit(QuasiAjaxSubmitButton.java:49)
at com.mycompany.myapp.web.comp.QuasiAjaxButton$1.onSubmit(QuasiAjaxButton.java:65)
at com.mycompany.myapp.web.comp.QuasiAjaxFormSubmitBehavior.onEvent(QuasiAjaxFormSubmitBehavior.java:151)
at org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:177)
at org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:286)
at org.apache.wicket.request.target.component.listener.BehaviorRequestTarget.processEvents(BehaviorRequestTarget.java:119)
at org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRequestCycleProcessor.java:92)
at org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1250)
at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329)
at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1428)
at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:479)
at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:312)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1139)
at org.springframework.orm.jpa.support.OpenEntityManagerInViewFilter.doFilterInternal(OpenEntityManagerInViewFilter.java:113)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1139)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:378)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:535)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:880)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)
com.mycompany.myapp.web.support.therapyend.TherapyEndSupportForm.onSaveFormData(TherapyEndSupportForm.java:135) 是我拨打therapyGroup.getToxicities().add(lastTherapy.getToxicity()); 的线路
【问题讨论】：
-
在同一行中还有另一个调用：lastTherapy.getToxicity()。你确定这不是问题吗？
-
如果没有完整的堆栈跟踪，包括所有“原因”部分，则无法回答此问题。就在昨天，我看到了这个确切的异常，其中“原因”显示数据库连接失败，即原因与代码无关。这可能不是你的问题，但除非我们能看到整个堆栈跟踪，否则答案可能是任何东西。
-
我已经添加了完整的堆栈跟踪。
-
为什么很临床：显然，当您在获取它的会话之外引用它时，治疗集合已经加载，而毒性集合则没有。在任何情况下，您都在尝试使用分离的实体而不首先对其进行管理；这是任何使用 Hibernate 的人都会遇到的这个令人难以置信的有据可查的异常的基础。一旦你研究了它背后的方式和原因，它的预期行为和非常合乎逻辑。
-
好的 Gimby，我如何管理它？
标签： java spring hibernate wicket lazy-initialization