org.springframework.transaction.UnexpectedRollbackException: Transaction rolled back because it has

最新推荐文章于 2025-08-12 10:00:00 发布

原创最新推荐文章于 2025-08-12 10:00:00 发布 · 1.6w 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#spring #log4j #object #logging #class #up

Exception 专栏收录该内容

16 篇文章

订阅专栏

本文探讨了Spring框架中@Transactional注解的使用方式及其潜在的问题。特别是当一个方法调用另一个被@Transactional标记的方法时，若发生异常如何正确处理以避免UnexpectedRollbackException错误。文章还提供了通过配置log4j进行Spring事务调试的方法。

@Transactional
    public void foo() {
        try{
            bar();
        } catch (RuntimeException re) {
            // caught but not throw further
            
        }
        
    }

    @Transactional
    public void bar() {
        
    }

如果foo在调用bar的时候，bar抛出RuntimeException，Spring在bar return时将Transactional标记为Rollback only，而foo捕获了bar的RuntimeException，所以Spring将会commit foo的事务，但是foo和bar使用的是同一事务，因此在commit foo事务时，将会抛出UnexpectedRollbackException。注意：如果foo和bar在同一class中，不会出现这种情况，因为：

Since this mechanism is based on proxies, only 'external' method calls coming in through the proxy will be intercepted. This means that 'self-invocation', i.e. a method within the target object calling some other method of the target object, won't lead to an actual transaction at runtime even if the invoked method is marked with @Transactional!

可以通过配置log4j来debug Spring事务获取情况：
To delve more into it I would turn up your log4j logging to debug and also look at what ExerciseModuleController is doing at line 91, e.g.: add a logger for org.springframework.transaction