转载：https://www.cnblogs.com/surging-dandelion/p/15085605.html

项目运行过程中，一个报错信息，报错信息如下：

org.hibernate.LazyInitializationException: could not initialize proxy [xxx.domain.Guild#CF12263C600F4BCABC9293D3FABE4B42] - no Session
    at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:169) ~[hibernate-core-5.3.9.Final.jar!/:5.3.9.Final]
    at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:309) ~[hibernate-core-5.3.9.Final.jar!/:5.3.9.Final]
    at org.hibernate.proxy.pojo.bytebuddy.ByteBuddyInterceptor.intercept(ByteBuddyInterceptor.java:45) ~[hibernate-core-5.3.9.Final.jar!/:5.3.9.Final]
    at org.hibernate.proxy.ProxyConfiguration$InterceptorDispatcher.intercept(ProxyConfiguration.java:95) ~[hibernate-core-5.3.9.Final.jar!/:5.3.9.Final]
    at xxx.domain.Guild$HibernateProxy$58NSae2j.getName(Unknown Source) ~[classes!/:0.0.9-SNAPSHOT]
    at xxx.task.TaskJiaoFuService.guildName(TaskJiaoFuService.java:181) ~[classes!/:0.0.9-SNAPSHOT]
    at xxx.task.TaskJiaoFuService.result2JiaoFuDetail(TaskJiaoFuService.java:122) ~[classes!/:0.0.9-SNAPSHOT]
    at xxx.task.TaskJiaoFuService.parseResult(TaskJiaoFuService.java:106) ~[classes!/:0.0.9-SNAPSHOT]
    at xxx.task.TaskJiaoFuService.queryV4(TaskJiaoFuService.java:91) ~[classes!/:0.0.9-SNAPSHOT]
    at xxx.AbstractExportStrategy.query(AbstractExportStrategy.java:65) ~[classes!/:0.0.9-SNAPSHOT]
    at xxx.ExportService.exportAndPersistence(ExportService.java:130) [classes!/:0.0.9-SNAPSHOT]
    at xxx.ExportService.lambda$execute$0(ExportService.java:75) [classes!/:0.0.9-SNAPSHOT]
    at xxx.common.initialization.ContextCopyingTaskDecorator.lambda$decorate$0(ContextCopyingTaskDecorator.java:20) ~[classes!/:0.0.9-SNAPSHOT]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[na:1.8.0_181]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[na:1.8.0_181]
    at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_181]

业务很简单，一个jpa的单表查询，获取属性的时候报错了

分析

JPA默认使用的懒加载，即使访问的是单个实体类，返回的对象也是代理，在获取对象属性的时候才会进行数据库查询，此时如果连接数据session已释放则会抛出上述异常
org.hibernate.LazyInitializationException在经常使用hibernate或者jpa的同学中可能经常遇到，网络上一搜，解决问题的方式有很多种，这里罗列一下：

• 在spring boot的配置文件application.properties添加spring.jpa.open-in-view=true
• 用spring 的OpenSessionInViewFilter
• 在spring boot的配置文件application.properties添加spring.jpa.properties.hibernate.enable_lazy_load_no_trans=true
• 在出问题的实体类上加@Proxy(lazy = false)
• ……

spring.jpa.open-in-view

我们看下baeldung上是怎么说的，传送门:https://www.baeldung.com/spring-open-session-in-view

Session per request is a transactional pattern to tie the persistence session and request life-cycles together. Not surprisingly, Spring comes with its own implementation of this pattern, named OpenSessionInViewInterceptor, to facilitate working with lazy associations and therefore, improving developer productivity.

………

By default, OSIV is active in Spring Boot applications. Despite that, as of Spring Boot 2.0, it warns us of the fact that it's enabled at application startup if we haven't configured it explicitly:

spring.jpa.open-in-view is enabled by default. Therefore, database 
queries may be performed during view rendering.Explicitly configure 
spring.jpa.open-in-view to disable this warning

意思大致是，每个请求会话对于Spring来说都是一种事务模式，所以了我们默认给你开启了，用于提高开发效率，不过你如果没有显式配置的话，我还会给你一个warning告警。关于这个默认配置在github上争论也有不少：https://github.com/spring-projects/spring-boot/issues/7107
OSIV时序图如下：

项目中spring.jpa.open-in-view是设置为false的，代码获取实体类或者关联实体都是service中完成的，一般我们开启事务，在事务作用的上下文环境中去获取懒加载的数据是不会有任何问题的，且开启之后数据的session会等到整个request完成之后才会释放，其实是十分消耗性能的，之前有其他同学没有关闭open-in-view遇到的问题：https://www.cnblogs.com/thisismarc/p/13594399.html

结论：spring.jpa.open-in-view为true可以解决报错，不过不推荐，OpenSessionInViewFilter配置方案也PASS

spring.jpa.properties.hibernate.enable_lazy_load_no_trans

我们也看下baeldung上是怎么说的，传送门:https://www.baeldung.com/hibernate-lazy-loading-workaround
While using lazy loading in Hibernate, we might face exceptions, saying there is no session.
……
The recommended approach is to design our application to ensure that data retrieval happens in a single transaction. But, this can sometimes be difficult when using a lazy entity in another part of the code that is unable to determine what has or hasn't been loaded.

Hibernate has a workaround, an enable_lazy_load_no_trans property. Turning this on means that each fetch of a lazy entity will open a temporary session and run inside a separate transaction.

意思大致是，这是一种变通的做法，可以为每个懒加载的实体打开一个临时的会话，不过这个方法也是反人类的，因为如果延迟加载的关联实体越多，请求附加的连接也就越多，这会给数据库连接带来压力。在新事务中加载的每个关联，在每次关联初始化后都会强制刷新事务日志，所以大大的不建议使用。

@Proxy(lazy = false)

@Proxy(lazy = false)的意思和FetchType.EAGER类似，返回的是初始化好的实体，即关闭了懒加载，这个肯定不是我们想要的

推荐解决方式

回到我们的问题，单表懒加载报错，项目使用的是Springboot，事务都是显式的注解配置，查询的接口我们一般没有配置@Transactional注解，所以解决方法是在Service的查询方法上增加 @Transactional(readOnly = true) 注解来划分事务边界，这是比较推荐的做法，也复合编码规范，项目中如果有事务切面配置，把相关方法加到事务控制的范围中则也不会出现这个问题，如果还有其他更好的方式，欢迎留言

参考链接

https://vladmihalcea.com/the-hibernate-enable_lazy_load_no_trans-anti-pattern/
https://www.baeldung.com/spring-open-session-in-view
https://github.com/spring-projects/spring-boot/issues/7107
https://www.cnblogs.com/thisismarc/p/13594399.html
https://www.baeldung.com/hibernate-lazy-loading-workaround