gpt4 book ai didi

Spring Transactions - 在未经检查的异常(RuntimeException)后防止回滚

转载 作者:行者123 更新时间:2023-12-01 00:55:53 25 4
gpt4 key购买 nike

我无法阻止事务在 RuntimeException 之后回滚.
我的环境是在 Websphere 8.0 上运行的 Spring 4.1 + Hibernate 3.6 + JTA (WebSphereUowTransactionManager)。
“doStuff”案例:有效
首先,一个表现符合预期的简单案例。自从我捕获 RuntimeException ,事务提交,新资源创建成功。

@Service("fooService")
public class FooServiceImpl implements IFooService {

@Transactional
@Override
public void doStuff(Resource res){
authService.createResource(res, "ADMIN");
try {
throw new RuntimeException("SOMETHING");
} catch (RuntimeException e) {
e.printStackTrace();
}
}
“doStuff2”案例:有效
下一个也可以。我声明 noRollbackFor 让我们提交事务:
    @Transactional(noRollbackFor=RuntimeException.class)
@Override
public void doStuff2(Resource res){
authService.createResource(res, "ADMIN");
throw new RuntimeException("SOMETHING");
}
“doStuff12”案例:不起作用
最后是有问题的。不同之处在于,在这种情况下,第二次调用 authService.createResource 会引发异常。 .仅供引用, authService.createResource仅标记为 @Transactional ,所以默认的传播配置适用,它应该加入调用服务的事务。
    @Transactional(noRollbackFor=RuntimeException.class)
@Override
public void doStuff12(Resource res){

authService.createResource(res, "ADMIN");
try{
res.setName("EXISTING-RESOURCE");
authService.createResource(res, "ADMIN");
}catch(RuntimeException e){
e.printStackTrace();
}
}
尽管 捕获 RuntimeException 并声明 noRollbackFor 属性事务总是回滚。有什么解释吗??
日志跟踪信息:
org.springframework.transaction.jta.WebSphereUowTransactionManager        DEBUG - Creating new transaction with name [null]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; '',+com.myorg.webapps.exception.ElementoYaExistente
org.springframework.transaction.jta.WebSphereUowTransactionManager DEBUG - Invoking WebSphere UOW action: type=1, join=false
org.springframework.transaction.support.TransactionSynchronizationManager TRACE - Initializing transaction synchronization
org.springframework.transaction.interceptor.TransactionInterceptor TRACE - Getting transaction for [com.myorg.test.service.impl.FooServiceImpl.doStuff12]
org.springframework.transaction.jta.WebSphereUowTransactionManager DEBUG - Creating new transaction with name [null]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; ''
org.springframework.transaction.jta.WebSphereUowTransactionManager DEBUG - Invoking WebSphere UOW action: type=1, join=true
org.springframework.transaction.interceptor.TransactionInterceptor TRACE - Getting transaction for [com.myorg.authmgr.service.impl.AuthorizationServiceImpl.createResource]
org.springframework.transaction.jta.WebSphereUowTransactionManager DEBUG - Returned from WebSphere UOW action: type=1, join=true
org.springframework.transaction.jta.WebSphereUowTransactionManager DEBUG - Creating new transaction with name [null]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; ''
org.springframework.transaction.jta.WebSphereUowTransactionManager DEBUG - Invoking WebSphere UOW action: type=1, join=true
org.springframework.transaction.interceptor.TransactionInterceptor TRACE - Getting transaction for [com.myorg.authmgr.service.impl.AuthorizationServiceImpl.createResource]
org.springframework.transaction.interceptor.RuleBasedTransactionAttribute TRACE - Applying rules to determine whether transaction should rollback on java.lang.Runtime: Couldn't create the resource, it already exists: EXISTING-RESOURCE
org.springframework.transaction.interceptor.RuleBasedTransactionAttribute TRACE - Winning rollback rule is: null
org.springframework.transaction.interceptor.RuleBasedTransactionAttribute TRACE - No relevant rollback rule found: applying default rules
org.springframework.transaction.jta.WebSphereUowTransactionManager DEBUG - Returned from WebSphere UOW action: type=1, join=true
org.springframework.transaction.jta.WebSphereUowTransactionManager TRACE - Triggering beforeCommit synchronization
org.springframework.transaction.jta.WebSphereUowTransactionManager TRACE - Triggering beforeCompletion synchronization
org.springframework.transaction.support.TransactionSynchronizationManager TRACE - Clearing transaction synchronization
org.springframework.transaction.jta.WebSphereUowTransactionManager DEBUG - Returned from WebSphere UOW action: type=1, join=false

最佳答案

据我所知,一旦从事务方法抛出运行时异常并被事务拦截器拦截,事务就会被标记为仅回滚。即使这个事务方法是从另一个事务方法调用的。

这对我来说很有意义:如果内部方法无法从异常中恢复,它就无法恢复,并且外部方法不应该像什么都没发生一样。

如果您希望事务不回滚,您可以

  • 使内部方法成为非事务性的
  • 配置内部方法不回滚此异常
  • 有两个内部方法:
  • 一个是事务性的,旨在在还没有事务时调用,它只是委托(delegate)给第二个
  • 非事务性的,旨在作为现有事务的一部分调用
  • 关于Spring Transactions - 在未经检查的异常(RuntimeException)后防止回滚,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/28090428/

    25 4 0
    Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
    广告合作:1813099741@qq.com 6ren.com