Spring源码剖析-Transactional 事务执行流程

doBegin(transaction, definition);

//针对当期线程的新事务同步设置

prepareSynchronization(status, definition);

return status;

}

catch (RuntimeException | Error ex) {

resume(null, suspendedResources);

throw ex;

}

}

else {

// Create “empty” transaction: no actual transaction, but potentially synchronization.

if (definition.getIsolationLevel() != TransactionDefinition.ISOLATION_DEFAULT && logger.isWarnEnabled()) {

logger.warn("Custom isolation level specified but no actual transaction initiated; " +

"isolation level will effectively be ignored: " + definition);

}

boolean newSynchronization = (getTransactionSynchronization() == SYNCHRONIZATION_ALWAYS);

//创建一个newTransactionStatus

return prepareTransactionStatus(definition, null, true, newSynchronization, debugEnabled, null);

}

}

该方法主要做了如下事情：

• 开启一个事务 创建了一个DataSourceTransactionObject 事务实例对象，其中绑定了ConnectionHolder，ConnectionHolder底层是ThreadLocal保存了当前线程的数据库连接信息。

• 如果当前线程存在事务，则转向嵌套事务的处理。

• 校验事务超时时间

• 如果事务传播机制是 PROPAGATION_MANDATORY ，如果不存在事务就抛异常

• 创建一个新的TransactionStatus：DefaultTransactionStatus。

• 完善事务信息设置ConnectionHolder、设置隔离级别、设置timeout，连接绑定到当前线程。

回顾一下事务传播行为：

| 事务传播行为类型 | 说明 |

| — | — |

| PROPAGATION_REQUIRED | 如果当前没有事务，就新建一个事务，如果已经存在一个事务中，加入到这个事务中。这是最常见的选择。 |

| PROPAGATION_SUPPORTS | 支持当前事务，如果当前没有事务，就以非事务方式执行。 |

| PROPAGATION_MANDATORY | 使用当前的事务，如果当前没有事务，就抛出异常。 |

| PROPAGATION_REQUIRES_NEW | 新建事务，如果当前存在事务，把当前事务挂起。 |

| PROPAGATION_NOT_SUPPORTED | 以非事务方式执行操作，如果当前存在事务，就把当前事务挂起。 |

| PROPAGATION_NEVER | 以非事务方式执行，如果当前存在事务，则抛出异常。 |

| PROPAGATION_NESTED | 如果当前存在事务，则在嵌套事务内执行。如果当前没有事务，则执行与PROPAGATION_REQUIRED类似的操作。 |

处理嵌套事务 ：handleExistingTransaction

//为现有事务创建 TransactionStatus。

private TransactionStatus handleExistingTransaction(

TransactionDefinition definition, Object transaction, boolean debugEnabled)

throws TransactionException {

//以非事务方式执行，如果当前存在事务，则抛出异常。

if (definition.getPropagationBehavior() == TransactionDefinition.PROPAGATION_NEVER) {

throw new IllegalTransactionStateException(

“Existing transaction found for transaction marked with propagation ‘never’”);

}

//以非事务方式执行操作，如果当前存在事务，就把当前事务挂起。并把事务信息设置为null

if (definition.getPropagationBehavior() == TransactionDefinition.PROPAGATION_NOT_SUPPORTED) {

if (debugEnabled) {

logger.debug(“Suspending current transaction”);

}

Object suspendedResources = suspend(transaction);

boolean newSynchronization = (getTransactionSynchronization() == SYNCHRONIZATION_ALWAYS);

return prepareTransactionStatus(

definition, null, false, newSynchronization, debugEnabled, suspendedResources);

}

//新建事务，如果当前存在事务，把当前事务挂起。当然会创建新的连接，让业务在新的事务中完成，之后恢复挂起的事务。

if (definition.getPropagationBehavior() == TransactionDefinition.PROPAGATION_REQUIRES_NEW) {

if (debugEnabled) {

logger.debug(“Suspending current transaction, creating new transaction with name [” +

definition.getName() + “]”);

}

SuspendedResourcesHolder suspendedResources = suspend(transaction);

try {

boolean newSynchronization = (getTransactionSynchronization() != SYNCHRONIZATION_NEVER);

//新开一个事务

DefaultTransactionStatus status = newTransactionStatus(

definition, transaction, true, newSynchronization, debugEnabled, suspendedResources);

doBegin(transaction, definition);

//初始化事务同步

prepareSynchronization(status, definition);

return status;

}

catch (RuntimeException | Error beginEx) {

resumeAfterBeginException(transaction, suspendedResources, beginEx);

throw beginEx;

}

}

//如果当前存在事务，则在嵌套事务内执行。如果当前没有事务，则执行与PROPAGATION_REQUIRED类似的操作。

if (definition.getPropagationBehavior() == TransactionDefinition.PROPAGATION_NESTED) {

//是否运行嵌套事务

if (!isNestedTransactionAllowed()) {

throw new NestedTransactionNotSupportedException(

"Transaction manager does not allow nested transactions by default - " +

“specify ‘nestedTransactionAllowed’ property with value ‘true’”);

}

if (debugEnabled) {

logger.debug(“Creating nested transaction with name [” + definition.getName() + “]”);

}

//对嵌套事务使用保存点

if (useSavepointForNestedTransaction()) {

// Create savepoint within existing Spring-managed transaction,

// through the SavepointManager API implemented by TransactionStatus.

// Usually uses JDBC 3.0 savepoints. Never activates Spring synchronization.

//如果是JDBC，使用保存点方式支持事务回滚

DefaultTransactionStatus status =

prepareTransactionStatus(definition, transaction, false, false, debugEnabled, null);

status.createAndHoldSavepoint();

return status;

}

else {

//如果是类似于JTA这种还无法使用保存点，处理方式如同PROPAGATION_REQUIRES_NEW

// Nested transaction through nested begin and commit/rollback calls.

// Usually only for JTA: Spring synchronization might get activated here

// in case of a pre-existing JTA transaction.

boolean newSynchronization = (getTransactionSynchronization() != SYNCHRONIZATION_NEVER);

DefaultTransactionStatus status = newTransactionStatus(

definition, transaction, true, newSynchronization, debugEnabled, null);

doBegin(transaction, definition);

prepareSynchronization(status, definition);

return status;

}

}

// Assumably PROPAGATION_SUPPORTS or PROPAGATION_REQUIRED.

if (debugEnabled) {

logger.debug(“Participating in existing transaction”);

}

if (isValidateExistingTransaction()) {

if (definition.getIsolationLevel() != TransactionDefinition.ISOLATION_DEFAULT) {

Integer currentIsolationLevel = TransactionSynchronizationManager.getCurrentTransactionIsolationLevel();

if (currentIsolationLevel == null || currentIsolationLevel != definition.getIsolationLevel()) {

Constants isoConstants = DefaultTransactionDefinition.constants;

throw new IllegalTransactionStateException(“Participating transaction with definition [” +

definition + "] specifies isolation level which is incompatible with existing transaction: " +

(currentIsolationLevel != null ?

isoConstants.toCode(currentIsolationLevel, DefaultTransactionDefinition.PREFIX_ISOLATION) :

“(unknown)”));

}

}

if (!definition.isReadOnly()) {

if (TransactionSynchronizationManager.isCurrentTransactionReadOnly()) {

throw new IllegalTransactionStateException(“Participating transaction with definition [” +

definition + “] is not marked as read-only but existing transaction is”);

}

}

}

boolean newSynchronization = (getTransactionSynchronization() != SYNCHRONIZATION_NEVER);

return prepareTransactionStatus(definition, transaction, false, newSynchronization, debugEnabled, null);

}

新开启事务：DataSourceTransactionManager#doBegin

/**

• This implementation sets the isolation level but ignores the timeout.

*/

@Override

protected void doBegin(Object transaction, TransactionDefinition definition) {

//创建 DataSource 事务对象

DataSourceTransactionObject txObject = (DataSourceTransactionObject) transaction;

Connection con = null;

try {

if (!txObject.hasConnectionHolder() ||

txObject.getConnectionHolder().isSynchronizedWithTransaction()) {

//获取连接

Connection newCon = obtainDataSource().getConnection();

if (logger.isDebugEnabled()) {

logger.debug(“Acquired Connection [” + newCon + “] for JDBC transaction”);

}

//把链接设置给DataSourceTransactionObject

txObject.setConnectionHolder(new ConnectionHolder(newCon), true);

}

txObject.getConnectionHolder().setSynchronizedWithTransaction(true);

con = txObject.getConnectionHolder().getConnection();

//设置事务隔离级别 ,使用, 以及ReadOnly

Integer previousIsolationLevel = DataSourceUtils.prepareConnectionForTransaction(con, definition);

txObject.setPreviousIsolationLevel(previousIsolationLevel);

// Switch to manual commit if necessary. This is very expensive in some JDBC drivers,

// so we don’t want to do it unnecessarily (for example if we’ve explicitly

// configured the connection pool to set it already).

if (con.getAutoCommit()) {

txObject.setMustRestoreAutoCommit(true);

if (logger.isDebugEnabled()) {

logger.debug(“Switching JDBC Connection [” + con + “] to manual commit”);

}

//设置手动提交,由Spring来控制事务提交

con.setAutoCommit(false);

}

prepareTransactionalConnection(con, definition);

//设置事务Active为true

txObject.getConnectionHolder().setTransactionActive(true);

//设置事务超时时间

int timeout = determineTimeout(definition);

if (timeout != TransactionDefinition.TIMEOUT_DEFAULT) {

txObject.getConnectionHolder().setTimeoutInSeconds(timeout);

}

//把连接绑定到当前线程

// Bind the connection holder to the thread.

if (txObject.isNewConnectionHolder()) {

TransactionSynchronizationManager.bindResource(obtainDataSource(), txObject.getConnectionHolder());

}

}

catch (Throwable ex) {

if (txObject.isNewConnectionHolder()) {

DataSourceUtils.releaseConnection(con, obtainDataSource());

txObject.setConnectionHolder(null, false);

}

throw new CannotCreateTransactionException(“Could not open JDBC Connection for transaction”, ex);

}

}

这个方法是事务开始的方法，因为它已经尝试和数据库进行连接了，然后又做了一些基础设置

• 设置事务的隔离级别，如果DB的隔离级别和事务属性源(TransactionAttribute )即：用户定义的事务隔离级别不一致，使用用户定义的隔离级别

• 把事务自动提交改为false,由Spring来控制事务提交

• 把 TransactionActive 状态设置为true,代表事务是active 激活状态

• 设置事务超时时间

• 把连接绑定到当前对象

到这， createTransactionIfNecessary 方法中的业务就分析完了，接下来就是 调用 invocation.proceedWithInvocation() 去执行目标类的方法，如果出现异常，会走catch中的回滚事务代码。

回滚事务：completeTransactionAfterThrowing

---

代码回到TransactionAspectSupport#invokeWithinTransaction ，我们跟一下completeTransactionAfterThrowing(txInfo, ex); 回滚事务代码，源码如下

protected void completeTransactionAfterThrowing(@Nullable TransactionInfo txInfo, Throwable ex) {

if (txInfo != null && txInfo.getTransactionStatus() != null) {

if (logger.isTraceEnabled()) {

logger.trace(“Completing transaction for [” + txInfo.getJoinpointIdentification() +

"] after exception: " + ex);

}

//判断异常类型决定是否要回滚

//默认判断异常是否是 RuntimeException 类型或者是 Error 类型

//可以指定异常处理类型，例如：@Transactional(rollbackFor=Exception.class)

if (txInfo.transactionAttribute != null && txInfo.transactionAttribute.rollbackOn(ex)) {

try {

//走事务管理器的rollback回滚事务

txInfo.getTransactionManager().rollback(txInfo.getTransactionStatus());

}

catch (TransactionSystemException ex2) {

logger.error(“Application exception overridden by rollback exception”, ex);

ex2.initApplicationException(ex);

throw ex2;

}

catch (RuntimeException | Error ex2) {

logger.error(“Application exception overridden by rollback exception”, ex);

throw ex2;

}

}

else {

// We don’t roll back on this exception.

// Will still roll back if TransactionStatus.isRollbackOnly() is true.

try {

//如果不满足回滚条件，即使抛出异常也同样会提交

txInfo.getTransactionManager().commit(txInfo.getTransactionStatus());

}

catch (TransactionSystemException ex2) {

logger.error(“Application exception overridden by commit exception”, ex);

ex2.initApplicationException(ex);

throw ex2;

}

catch (RuntimeException | Error ex2) {

logger.error(“Application exception overridden by commit exception”, ex);

throw ex2;

}

}

}

}

首先是判断了异常的类型符不符合回滚条件，如果符合就调用事务管理器的回滚逻辑，如果不符合回滚条件就走事务管理器的commit提交事务，下面是回滚逻辑：AbstractPlatformTransactionManager#rollback

@Override

public final void rollback(TransactionStatus status) throws TransactionException {

if (status.isCompleted()) {

throw new IllegalTransactionStateException(

“Transaction is already completed - do not call commit or rollback more than once per transaction”);

}

//事务状态

DefaultTransactionStatus defStatus = (DefaultTransactionStatus) status;

//处理回滚

processRollback(defStatus, false);

}

/**

• Process an actual rollback.

• The completed flag has already been checked.

• @param status object representing the transaction

• @throws TransactionException in case of rollback failure

*/

private void processRollback(DefaultTransactionStatus status, boolean unexpected) {

try {

boolean unexpectedRollback = unexpected;

try {

//触发事务同步器TransactionSynchronization中的beforeCompletion回调

//比如调用SqlSessionSynchronization#beforeCompletion 释放资源，sqlSession close等

triggerBeforeCompletion(status);

//如果有保存点，回滚到保存点

if (status.hasSavepoint()) {

if (status.isDebug()) {

logger.debug(“Rolling back transaction to savepoint”);

}

status.rollbackToHeldSavepoint();

}

else if (status.isNewTransaction()) {

//如果是新开的事务，直接触发回滚，

if (status.isDebug()) {

logger.debug(“Initiating transaction rollback”);

}

//走的是 Connection.rollback回滚

doRollback(status);

}

else {

// Participating in larger transaction

// 如果当前事务不是独立的事务，那么只能标记状态，等到事务链执行完毕后统一回滚

if (status.hasTransaction()) {

if (status.isLocalRollbackOnly() || isGlobalRollbackOnParticipationFailure()) {

if (status.isDebug()) {

logger.debug(“Participating transaction failed - marking existing transaction as rollback-only”);

}

doSetRollbackOnly(status);

}

else {

if (status.isDebug()) {

logger.debug(“Participating transaction failed - letting transaction originator decide on rollback”);

}

}

}

else {

logger.debug(“Should roll back transaction but cannot - no transaction available”);

}

// Unexpected rollback only matters here if we’re asked to fail early

if (!isFailEarlyOnGlobalRollbackOnly()) {

unexpectedRollback = false;

}

}

}

catch (RuntimeException | Error ex) {

triggerAfterCompletion(status, TransactionSynchronization.STATUS_UNKNOWN);

throw ex;

}

// 触发所有 TransactionSynchronization 同步器中对应的 afterCompletion 方法

//比如调用 SqlSessionSynchronization#beforeCompletion 释放资源，重置SqlSession等

triggerAfterCompletion(status, TransactionSynchronization.STATUS_ROLLED_BACK);

// Raise UnexpectedRollbackException if we had a global rollback-only marker

if (unexpectedRollback) {

throw new UnexpectedRollbackException(

“Transaction rolled back because it has been marked as rollback-only”);

}

}

finally {

//执行清空资源 ， 恢复挂起的资源

cleanupAfterCompletion(status);

}

}

总结一下回滚逻辑

• 触发TransactionSynchronization中的beforeCompletion回调 ， TransactionSynchronization定义是事务同步逻辑。比如：SqlSessionSynchronization#beforeCompletion 就用来释放资源，sqlSession close等

• 如果有保存点，就使用保存点信息进行回滚

• 如果是新开的是事务，使用底层数据库的API回滚

• 其他情况比如JTA模式就标记回滚，等到提交的时候统一回滚

事务清理：cleanupAfterCompletion

private void cleanupAfterCompletion(DefaultTransactionStatus status) {

//设置完成状态

status.setCompleted();

if (status.isNewSynchronization()) {

//事务同步管理器清理

TransactionSynchronizationManager.clear();

}

if (status.isNewTransaction()) {

doCleanupAfterCompletion(status.getTransaction());

}

if (status.getSuspendedResources() != null) {

if (status.isDebug()) {

logger.debug(“Resuming suspended transaction after completion of inner transaction”);

}

Object transaction = (status.hasTransaction() ? status.getTransaction() : null);

//恢复挂起的事务：

resume(transaction, (SuspendedResourcesHolder) status.getSuspendedResources());

}

}

1. 如果是新的同步状态，则走TransactionSynchronizationManager.clear();清除当前线程的整个事务同步状态

2. 如果是新开的事务，则走doCleanupAfterCompletion清理资源，该方法做了如下事情：

• 把数据库连接和当前线程解绑

• 重置连接，设置自动提交为true

• 如果是新开的事务，就释放连接对象

• 清空ConnectionHolder

3. 如果之前有挂起的事务，就走resume恢复

事务提交：commitTransactionAfterReturning

---

protected void commitTransactionAfterReturning(@Nullable TransactionInfo txInfo) {

if (txInfo != null && txInfo.getTransactionStatus() != null) {

if (logger.isTraceEnabled()) {

logger.trace(“Completing transaction for [” + txInfo.getJoinpointIdentification() + “]”);

}

txInfo.getTransactionManager().commit(txInfo.getTransactionStatus());

}

}

@Override

public final void commit(TransactionStatus status) throws TransactionException {

if (status.isCompleted()) {

throw new IllegalTransactionStateException(

“Transaction is already completed - do not call commit or rollback more than once per transaction”);

}

DefaultTransactionStatus defStatus = (DefaultTransactionStatus) status;

//如果事务被标记回滚，直接回滚

if (defStatus.isLocalRollbackOnly()) {

if (defStatus.isDebug()) {

logger.debug(“Transactional code has requested rollback”);

}

//走回滚流程

processRollback(defStatus, false);

return;

}

if (!shouldCommitOnGlobalRollbackOnly() && defStatus.isGlobalRollbackOnly()) {

if (defStatus.isDebug()) {

logger.debug(“Global transaction is marked as rollback-only but transactional code requested commit”);

}

processRollback(defStatus, true);

return;

}

//执行提交流程

processCommit(defStatus);

}

提交事务之前会先判断是否要回滚，然后触发回滚，否则就正常走提交事务流程

private void processCommit(DefaultTransactionStatus status) throws TransactionException {

try {

boolean beforeCompletionInvoked = false;

try {

boolean unexpectedRollback = false;

prepareForCommit(status);

//调用 同步器的beforeCommit ：比如走 SqlSessionSynchronization#beforeCommit执行 SqlSession().commit() 提交事务

triggerBeforeCommit(status);

//触发同步器的beforeCompletion，比如走：SqlSessionSynchronization#beforeCompletion 解绑资源，执行sqlSession.close

triggerBeforeCompletion(status);

beforeCompletionInvoked = true;

//如果有保存点

if (status.hasSavepoint()) {

if (status.isDebug()) {

logger.debug(“Releasing transaction savepoint”);

}

unexpectedRollback = status.isGlobalRollbackOnly();

//释放保存点

status.releaseHeldSavepoint();

}

//如果是新开事务

else if (status.isNewTransaction()) {

if (status.isDebug()) {

logger.debug(“Initiating transaction commit”);

}

unexpectedRollback = status.isGlobalRollbackOnly();

//调用collection.commit 提交事务

最后

看完上述知识点如果你深感Java基础不够扎实，或者刷题刷的不够、知识不全面

小编专门为你量身定制了一套<Java一线大厂高岗面试题解析合集：JAVA基础-中级-高级面试+SSM框架+分布式+性能调优+微服务+并发编程+网络+设计模式+数据结构与算法>

针对知识面不够，也莫慌！还有一整套的<Java核心进阶手册>，可以瞬间查漏补缺

全都是一丢一丢的收集整理纯手打出来的

更有纯手绘的各大知识体系大纲，可供梳理：Java筑基、MySQL、Redis、并发编程、Spring、分布式高性能架构知识、微服务架构知识、开源框架知识点等等的xmind手绘图~

加入社区：https://bbs.csdn.net/forums/4304bb5a486d4c3ab8389e65ecb71ac0
ked = true;

//如果有保存点

if (status.hasSavepoint()) {

if (status.isDebug()) {

logger.debug(“Releasing transaction savepoint”);

}

unexpectedRollback = status.isGlobalRollbackOnly();

//释放保存点

status.releaseHeldSavepoint();

}

//如果是新开事务

else if (status.isNewTransaction()) {

if (status.isDebug()) {

logger.debug(“Initiating transaction commit”);

}

unexpectedRollback = status.isGlobalRollbackOnly();

//调用collection.commit 提交事务

最后

看完上述知识点如果你深感Java基础不够扎实，或者刷题刷的不够、知识不全面

小编专门为你量身定制了一套<Java一线大厂高岗面试题解析合集：JAVA基础-中级-高级面试+SSM框架+分布式+性能调优+微服务+并发编程+网络+设计模式+数据结构与算法>

[外链图片转存中…(img-P2sATIbR-1725744742437)]

针对知识面不够，也莫慌！还有一整套的<Java核心进阶手册>，可以瞬间查漏补缺

[外链图片转存中…(img-a75rZh8f-1725744742437)]

全都是一丢一丢的收集整理纯手打出来的

更有纯手绘的各大知识体系大纲，可供梳理：Java筑基、MySQL、Redis、并发编程、Spring、分布式高性能架构知识、微服务架构知识、开源框架知识点等等的xmind手绘图~

[外链图片转存中…(img-asO1fo6z-1725744742438)]

[外链图片转存中…(img-K6CDzztS-1725744742438)]

加入社区：https://bbs.csdn.net/forums/4304bb5a486d4c3ab8389e65ecb71ac0