最近在開發的過程中遇到了使用Transaction marked as rollback only的問題,瞭解到報錯的原因:

應該是事務被rollback了多次導致的錯誤。仔細看程式碼,由於專案中在aop切面、控制層、service分別開啟了一次事務,而在service裡報錯的時候本來在service層已經進行了一次rollback,但是由於在aop環繞切面的時候也開啟了事務,捕獲到了來自service的異常,於是同一個事務就進行了rollback兩次(僅是個人經驗的猜測,文章有錯請各位大佬指出)
@Transactional配置:
事務隔離級別:TransactionDefinition.ISOLATION_DEFAULT
事務傳播行為:TransactionDefinition.PROPAGATION_REQUIRED

解決方案

在org.springframework.transaction.support.AbstractPlatformTransactionManager 中有個叫
isGlobalRollbackOnParticipationFailure的引數，預設是true.
原始碼中說明：

Switch this to “false” to let the transaction originator make the rollback decision. If a participating transaction fails with an exception, the caller can still decide to continue with a different path within the transaction. However, note that this will only work as long as all participating resources are capable of continuing towards a transaction commit even after a data access failure: This is generally not the case for a Hibernate Session, for example; neither is it for a sequence of JDBC insert/update/delete operations.

大意是：如果isGlobalRollbackOnParticipationFailure為false,則會讓主事務決定回滾，如果當遇到exception加入事務失敗時，呼叫者能繼續在事務內決定是回滾還是繼續。然而，要注意是那樣做僅僅適用於在資料訪問失敗的情況下且只要所有操作事務能提交。

xml

<bean id="transactionManager" class="org.springframework.orm.hibernate3.HibernateTransactionManager">
  <property name="sessionFactory"
 
>
   <ref bean="sessionFactory" />
  </property>
  <property name="globalRollbackOnParticipationFailure" value="false" />
 </bean>

spring-boot

@Configuration
@Lazy
@MapperScan("cn.blockchain.core.mapper")
@EnableTransactionManagement(order = 8)
public class TransactionConfig {
    @Bean
    public PlatformTransactionManager txManager(com.alibaba.druid.pool.DruidDataSource dataSource) {
        DataSourceTransactionManager dataSourceTransactionManager = new DataSourceTransactionManager(dataSource);
        dataSourceTransactionManager.setGlobalRollbackOnParticipationFailure(false);
        return dataSourceTransactionManager;
    }
}

參考: