解决Spring4+Hibernate4遇到的 Write operations are not allowed in read-only mode (FlushMode.MANUAL)

最新推荐文章于 2025-05-21 08:40:32 发布

原创最新推荐文章于 2025-05-21 08:40:32 发布 · 6.7k 阅读

1 ·

CC 4.0 BY-SA版权

本文介绍了解决Spring框架中DAO层出现的Writeoperationsarenotallowedinread-onlymode错误的方法。通过正确配置事务属性，特别是针对读写操作的不同场景。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

全部的错误stack类似：

org.springframework.dao.InvalidDataAccessApiUsageException: Write operations are not allowed in read-only mode (FlushMode.MANUAL): Turn your Session into FlushMode.COMMIT/AUTO or remove 'readOnly' marker from transaction definition.
   at org.springframework.orm.hibernate4.HibernateTemplate.checkWriteOperationAllowed(HibernateTemplate.java:1135)
   at org.springframework.orm.hibernate4.HibernateTemplate$12.doInHibernate(HibernateTemplate.java:620)
   at org.springframework.orm.hibernate4.HibernateTemplate$12.doInHibernate(HibernateTemplate.java:617)
   at org.springframework.orm.hibernate4.HibernateTemplate.doExecute(HibernateTemplate.java:340)
   at org.springframework.orm.hibernate4.HibernateTemplate.executeWithNativeSession(HibernateTemplate.java:308)
   at org.springframework.orm.hibernate4.HibernateTemplate.save(HibernateTemplate.java:617)
   at com.sac.capital.dao.GenericDaoImpl.create(GenericDaoImpl.java:36)
   at com.sac.capital.dao.test.TestDaoImplTest.test(TestDaoImplTest.java:35)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:606)
   at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
   at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
   at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
   at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
   at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
   at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
   at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
   at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
   at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
   at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
   at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
   at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
   at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
   at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)

我相信很多人应该都遇到了吧，我也搜了google，不过给的答案都不尽人意。其实原因正如stack所写：当FlushMode为Manual时，不能在readonly情况下进行写操作。

如果你在写DAO层，然后又对DAO进行test，DAO的class的事务声明都是默认的话，就会遇到上面这个错误。

那么我们先把service和dao全部写好，然后把service层的声明式事务也配置好：通常如下：

    <tx:advice id="txAdvice" transaction-manager="txManager">
       <tx:attributes>
           <tx:method name="save*" propagation="REQUIRED" />
           <tx:method name="add*" propagation="REQUIRED" />
           <tx:method name="create*" propagation="REQUIRED" />
           <tx:method name="insert*" propagation="REQUIRED" />
           <tx:method name="update*" propagation="REQUIRED" />
           <tx:method name="merge*" propagation="REQUIRED" />
           <tx:method name="del*" propagation="REQUIRED" />
           <tx:method name="remove*" propagation="REQUIRED" />
           <tx:method name="put*" propagation="REQUIRED" />
           <tx:method name="use*" propagation="REQUIRED" />

           <tx:method name="get*" propagation="REQUIRED" read-only="true" />
           <tx:method name="count*" propagation="REQUIRED" read-only="true" />
           <tx:method name="find*" propagation="REQUIRED" read-only="true" />
           <tx:method name="list*" propagation="REQUIRED" read-only="true" />
           <tx:method name="*" read-only="true" />
       </tx:attributes>
   </tx:advice>
   <aop:config expose-proxy="true">
       <aop:pointcut id="txPointcut" expression="execution(* com.sac.capital.service..*.*(..))" />
       <aop:advisor advice-ref="txAdvice" pointcut-ref="txPointcut" />
   </aop:config>

然后再对Service的类进行测试，数据库操作完全成功。但单独对Dao的类测试，数据库写操作还是会报这个错误。

（这里我是觉得Service和DAO两层，没必要都写unit test啦，但如果你项目非要全都写，请继续看下去）

到了这里，你也知道这错误是怎么出来地，就是因为DAO层完全没有事务的声明, 所以给DAO也加上事务声明把：

    <aop:config expose-proxy="true">
       <aop:pointcut id="txPointcut" expression="execution(* com.sac.capital.dao..*.*(..))" />
       <aop:advisor advice-ref="txAdvice" pointcut-ref="txPointcut" />
   </aop:config>

后来深入研究发现，上面那段copy来的声明式事务其实写的也不好，应该改成：

    <tx:advice id="txAdvice" transaction-manager="txManager">
       <tx:attributes>
           <tx:method name="get*" propagation="SUPPORTS" read-only="true" />
           <tx:method name="count*" propagation="SUPPORTS" read-only="true" />
           <tx:method name="find*" propagation="SUPPORTS" read-only="true" />
           <tx:method name="list*" propagation="SUPPORTS" read-only="true" />
           <tx:method name="*" read-only="false" propagation="REQUIRED" />
       </tx:attributes>
   </tx:advice>

是不是更好点？？？