hibernate的executeWithNativeSession(HibernateCallbk())、execute(new HibernateCallback())无法对spring事务回滚

hibernate作为DAO使用如下的方法操作数据库时,无法对spring在service层添加的事务进行回滚。

        hibernateTemplate.executeWithNativeSession(new HibernateCallback() {
            @Override
            public Object doInHibernate(Session session) throws HibernateException, SQLException {
                session.beginTransaction();
                SQLQuery sqlQuery = session.createSQLQuery("DELETE  FROM  teacher_class_check where teacher_id=:teacherId AND class_id=:classId");
                Query query = sqlQuery.setString("teacherId",teacherId).setString("classId",classId);
                query.executeUpdate();
                session.getTransaction().commit();
                return null;
            }
        });
hibernateTemplate.execute(new HibernateCallback() {
            @Override
            public Object doInHibernate(Session session) throws HibernateException, SQLException {
                session.beginTransaction();
                SQLQuery sqlQuery = session.createSQLQuery("DELETE  FROM  teacher_class_check where teacher_id=:teacherId AND class_id=:classId");
                Query query = sqlQuery.setString("teacherId",teacherId).setString("classId",classId);
                query.executeUpdate();
                session.getTransaction().commit();
                return null;
            }
        });

下面是尝试回滚时的堆栈信息。无法开启事务。(但同一个地方我使用其他方法操作数据库可以回滚)


04-Sep-2016 15:04:13.013 SEVERE [http-nio-8080-exec-8] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [newClassProject] in context with path [] threw exception [Request processing failed; nested exception is org.springframework.transaction.TransactionSystemException: Could not roll back Hibernate transaction; nested exception is org.hibernate.TransactionException: Transaction not successfully started] with root cause
 org.hibernate.TransactionException: Transaction not successfully started
    at org.hibernate.transaction.JDBCTransaction.rollback(JDBCTransaction.java:183)
    at org.springframework.orm.hibernate3.HibernateTransactionManager.doRollback(HibernateTransactionManager.java:676)
    at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:845)
    at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:822)
    at org.springframework.transaction.interceptor.TransactionAspectSupport.completeTransactionAfterThrowing(TransactionAspectSupport.java:412)
    at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:114)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
    at com.sun.proxy.$Proxy20.emptyData(Unknown Source)
    at com.shusheng.controller.CheckController.emptyData(CheckController.java:116)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.springframework.web.bind.annotation.support.HandlerMethodInvoker.invokeHandlerMethod(HandlerMethodInvoker.java:176)
    at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.invokeHandlerMethod(AnnotationMethodHandlerAdapter.java:436)
    at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.handle(AnnotationMethodHandlerAdapter.java:424)
    at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)
    at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)
    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
    at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
    at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)
    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
    at org.apache.catalina.core.StandardContextValve.__invoke(StandardContextValve.java:108)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:522)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
    at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:620)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:349)
    at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:1110)
    at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
    at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:785)
    at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1425)
    at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
    at java.lang.Thread.run(Thread.java:745)

源码看的有点蒙,如果大神知道为什么欢迎留言。

  • 1
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Spring 中,可以使用 `@Transactional` 注解来开启事务。在多线程环境下,如果需要控制事务回滚,可以采用以下两种方式: 1. 在子线程中捕获异常并手动回滚事务 在子线程中进行数据库操作时,如果出现异常,可以手动回滚事务。具体实现步骤如下: - 在父线程中开启事务,将事务对象传递给子线程。 - 在子线程中进行数据库操作,如果出现异常则手动回滚事务。 - 在父线程中判断子线程是否抛出异常,如果有异常则回滚事务。 ``` @Service public class UserService { @Autowired private PlatformTransactionManager transactionManager; @Transactional public void doSomethingInTransaction() { // 在父线程中开启事务 DefaultTransactionDefinition definition = new DefaultTransactionDefinition(); TransactionStatus status = transactionManager.getTransaction(definition); try { // 在子线程中进行数据库操作 CompletableFuture<Void> future = CompletableFuture.runAsync(() -> { // 获取子线程的事务对象 TransactionStatus childStatus = TransactionAspectSupport.currentTransactionStatus(); try { // 子线程中进行数据库操作 // ... } catch (Exception e) { // 手动回滚子线程的事务 transactionManager.rollback(childStatus); throw e; } }); // 等待子线程执行完毕 future.get(); // 判断子线程是否抛出异常,如果有异常则回滚事务 if (future.isCompletedExceptionally()) { throw new RuntimeException("子线程执行出错"); } // 提交事务 transactionManager.commit(status); } catch (Exception e) { // 回滚事务 transactionManager.rollback(status); throw e; } } } ``` 2. 使用 Spring 的 `TransactionTemplate` 来控制事务回滚 Spring 提供了 `TransactionTemplate` 类来简化事务的编程。可以通过 `TransactionTemplate` 的 `execute()` 方法来执行数据库操作,如果出现异常则自动回滚事务。具体实现步骤如下: - 在父线程中使用 `TransactionTemplate` 开启事务。 - 在子线程中使用 `TransactionTemplate` 执行数据库操作。 - 如果子线程抛出异常,则 `TransactionTemplate` 会自动回滚事务。 ``` @Service public class UserService { @Autowired private PlatformTransactionManager transactionManager; public void doSomethingInTransaction() { // 使用 TransactionTemplate 开启事务 TransactionTemplate template = new TransactionTemplate(transactionManager); template.execute(new TransactionCallbackWithoutResult() { @Override protected void doInTransactionWithoutResult(TransactionStatus status) { // 在子线程中使用 TransactionTemplate 执行数据库操作 CompletableFuture<Void> future = CompletableFuture.runAsync(() -> { template.execute(new TransactionCallbackWithoutResult() { @Override protected void doInTransactionWithoutResult(TransactionStatus childStatus) { // 子线程中进行数据库操作 // ... } }); }); // 等待子线程执行完毕 future.join(); } }); } } ``` 无论使用哪种方式,都需要注意事务的传播机制。默认情况下,事务的传播机制是 `Propagation.REQUIRED`,即如果当前没有事务,则开启一个新的事务;如果当前已经存在事务,则加入该事务中。如果需要修改传播机制,可以在 `@Transactional` 注解中进行设置。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值