Transaction rolled back because it has been marked as rollback-only

翎野君

发布于 2024-04-10 08:05:20

2260

发布于 2024-04-10 08:05:20

文章被收录于专栏：翎野君

背景

最近在看程序日志的时候，发现频繁出现 Transaction rolled back because it has been marked as rollback-only这个异常，查了很久资料才知道是什么原因导致抛出这异常的，下面解析一下；

原因

字面上的意思就是：事务已回滚，因为它已被标记为仅回滚，那为什么会标记为仅回滚呢？

其实原因就是嵌套事务导致的，因为spring事务有传递性，spring默认的事务传播级别是PROPAGATION_REQUIRED，即当前上下文存在事务则用此事务，如果不存在事务则新建一个事务执行；

那么现在有A和B两个方法，这两个方法都开启了事务，A方法中调用B方法（因为都使用事务，默认的事务传播级别是PROPAGATION_REQUIRED，所以这过程中会使用同一个事务）；

当执行B方法的时候，B方法抛出异常，这个时候事务就会被标记为仅回滚（因为在B方法中抛出异常，B方法这事务本该是要回滚，所以会将B方法的事务标记为rollback-only）；

但是在A方法又catch到B方法抛的异常，但是A方法catch到异常后没有继续往上抛出，而是继续执行后面的代码，最后正常提交事务，那么就会抛出 Transaction rolled back because it has been marked as rollback-only这异常！（因为AB是用同一个事务，在B方法执行的时候这个事务就标记为rollback-only，然后A方法继续使用该事务，然后又执行事务提交的操作，所以最后会抛异常）

事例

public void a() {
        try {
            SysInterfaceLogSettintModel model = new SysInterfaceLogSettintModel();
            model.setInterfaceCode("code");
            model.setInterfaceName("name");
            //这里做了保存操作
            this.save(model);
            //这里调用了b方法，是另外一个service的
            roleMenuService.b();
            //执行完提交事务
        }catch (Exception e ){
        	//a方法catch了异常但是没有继续抛出，事务会提交
            e.printStackTrace();
        }
    }
   
	public void b() throws Exception {
		//b方法抛出异常
		throw new Exception("Exception");
	}

最后会抛出异常

org.springframework.transaction.UnexpectedRollbackException: Transaction rolled back because it has been marked as rollback-only
	at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:724)
	at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:485)
	at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:291)
	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
	at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655)
	at java.util.ArrayList.forEach(ArrayList.java:1249)
	at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
	at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
	at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:85)
	at sun.reflect.GeneratedMethodAccessor3052.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:620)
	at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:609)
	at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:68)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:168)
	at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
	at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655)
	at com.dangdang.ddframe.job.executor.type.SimpleJobExecutor.process(SimpleJobExecutor.java:41)
	at com.dangdang.ddframe.job.executor.AbstractElasticJobExecutor.process(AbstractElasticJobExecutor.java:207)
	at com.dangdang.ddframe.job.executor.AbstractElasticJobExecutor.access$000(AbstractElasticJobExecutor.java:47)
	at com.dangdang.ddframe.job.executor.AbstractElasticJobExecutor$1.run(AbstractElasticJobExecutor.java:186)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:108)
	at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:41)
	at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:77)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

本篇文章如有帮助到您，请给「翎野君」点个赞，感谢您的支持。

首发链接： https://cloud.tencent.com/developer/article/2406894

本文参与腾讯云自媒体同步曝光计划，分享自作者个人站点/博客。

原始发表：2024-04-09，如有侵权请联系 cloudcommunity@tencent.com 删除

marked