JDBC事务中如何保证TCC的原子性
在java jdbc环境下实现批量操作的tcc(try-confirm-cancel)模式,核心在于利用数据库的事务隔离级别和手动提交机制。具体做法是:在try阶段开启jdbc事务,执行所有资源的预占操作(如扣减库存、冻结资金),若全部成功则提交事务;若任一环节失败,则回滚事务并触发cancel流程。这种机制确保了try阶段的“全有或全无”特性,为后续的confirm或cancel提供了可靠的基础。

批量操作中Try与Cancel的异常处理策略
针对批量操作中的异常处理,关键在于区分“可重试”与“不可重试”错误,并确保Cancel逻辑能正确识别未完成的Try状态。具体做法是:在Try阶段捕获特定异常(如死锁、超时),记录事务ID并标记状态为“待取消”,随后立即回滚JDBC事务;在Cancel阶段,通过查询数据库中的状态标记,仅对处于“待取消”状态的业务记录执行反向操作(如解冻资金)。这种策略避免了因网络抖动导致的重复Try或无效Cancel。

基于JDBC自动提交关闭的具体配置问题
在JDBC中实现TCC时,必须显式关闭autoCommit属性,否则无法控制事务边界。具体做法是:调用connection.setAutoCommit(false),并在Try阶段的所有SQL执行完毕后,根据结果调用connection.commit()或connection.rollback()。若不关闭自动提交,每条SQL都会独立提交,导致Try阶段部分成功部分失败,破坏TCC的一致性要求。
立即学习“Java免费学习笔记(深入)”;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.SQLException;
public class TccBatchExample {
public static void main(String[] args) {
String url = "jdbc:mysql://localhost:3306/mydb";
String user = "root";
String password = "password";
// 模拟批量数据
int[] amounts = {100, 200, 300};
try (Connection conn = DriverManager.getConnection(url, user, password)) {
// 关键步骤1:关闭自动提交
conn.setAutoCommit(false);
String sql = "UPDATE accounts SET balance = balance - ? WHERE id = ?";
PreparedStatement pstmt = conn.prepareStatement(sql);
boolean allSuccess = true;
for (int i = 0; i < amounts.length; i++) {
pstmt.setInt(1, amounts[i]);
pstmt.setInt(2, i + 1); // 假设账户ID为1,2,3
int rowsAffected = pstmt.executeUpdate();
if (rowsAffected == 0) {
allSuccess = false;
break; // 任一失败,跳出循环
}
}
if (allSuccess) {
conn.commit(); // Try成功,提交事务
System.out.println("Try阶段完成,事务已提交");
} else {
conn.rollback(); // Try失败,回滚事务
System.out.println("Try阶段失败,事务已回滚,需触发Cancel");
}
} catch (SQLException e) {
e.printStackTrace();
}
}
}
上述代码展示了基本的TCC Try阶段实现。输入为三个金额数组{100, 200, 300},预期结果是:若所有账户余额充足,则事务提交,输出“Try阶段完成,事务已提交”;若任一账户余额不足(导致rowsAffected == 0),则事务回滚,输出“Try阶段失败,事务已回滚,需触发Cancel”。注意,实际生产中需结合分布式事务协调器(如Seata)管理全局事务状态,此处仅展示JDBC层面的基础控制。
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
public class TccCancelExample {
public static void main(String[] args) {
String url = "jdbc:mysql://localhost:3306/mydb";
String user = "root";
String password = "password";
// 模拟需要取消的交易ID
String transactionId = "TXN_001";
try (Connection conn = DriverManager.getConnection(url, user, password)) {
// 关键步骤:关闭自动提交,确保Cancel操作的原子性
conn.setAutoCommit(false);
// 查询Try阶段的状态
String querySql = "SELECT status FROM transactions WHERE txn_id = ?";
PreparedStatement queryPstmt = conn.prepareStatement(querySql);
queryPstmt.setString(1, transactionId);
ResultSet rs = queryPstmt.executeQuery();
if (rs.next()) {
String status = rs.getString("status");
if ("TRY_PENDING".equals(status)) {
// 执行Cancel逻辑:恢复资源
String cancelSql = "UPDATE accounts SET balance = balance + ? WHERE id = ?";
PreparedStatement cancelPstmt = conn.prepareStatement(cancelSql);
// 假设之前Try阶段扣减的金额和账户ID
int amount = 100;
int accountId = 1;
cancelPstmt.setInt(1, amount);
cancelPstmt.setInt(2, accountId);
cancelPstmt.executeUpdate();
// 更新交易状态为CANCELLED
String updateSql = "UPDATE transactions SET status = 'CANCELLED' WHERE txn_id = ?";
PreparedStatement updatePstmt = conn.prepareStatement(updateSql);
updatePstmt.setString(1, transactionId);
updatePstmt.executeUpdate();
conn.commit(); // Cancel成功,提交事务
System.out.println("Cancel阶段完成,资源已恢复");
} else {
System.out.println("交易状态不是TRY_PENDING,无需Cancel");
}
}
} catch (SQLException e) {
e.printStackTrace();
}
}
}
此代码演示了Cancel阶段的实现。输入为交易ID"TXN_001",预期结果是:若数据库中该交易状态为"TRY_PENDING",则执行反向SQL更新账户余额,并将状态改为"CANCELLED",最后提交事务,输出“Cancel阶段完成,资源已恢复”;若状态非"TRY_PENDING",则跳过Cancel逻辑,输出“交易状态不是TRY_PENDING,无需Cancel”。这确保了Cancel操作的幂等性和安全性。
digraph G {
rankdir=LR;
node [shape=box, style=filled, fillcolor=lightblue, fontsize=16];
edge [fontsize=16];
Start [label="开始TCC批量操作", shape=diamond, fillcolor=yellow];
OpenTxn [label="开启JDBC事务\nsetAutoCommit(false)"];
ExecuteTry [label="执行批量Try SQL\n扣减/冻结资源"];
CheckResult [label="检查Try结果\n是否全部成功?", shape=diamond];
CommitTxn [label="提交事务\ncommit()"];
RollbackTxn [label="回滚事务\nrollback()"];
TriggerCancel [label="触发Cancel流程"];
EndSuccess [label="Try成功结束", shape=doublecircle];
EndFail [label="Try失败结束", shape=doublecircle];
Start -> OpenTxn;
OpenTxn -> ExecuteTry;
ExecuteTry -> CheckResult;
CheckResult -> CommitTxn [label="是"];
CheckResult -> RollbackTxn [label="否"];
CommitTxn -> EndSuccess;
RollbackTxn -> TriggerCancel;
TriggerCancel -> EndFail;
}
<pre class="brush:php;toolbar:false;">digraph G {
rankdir=TB;
node [shape=ellipse, style=filled, fillcolor=lightyellow, fontsize=16];
edge [fontsize=16];
TryPhase [label="Try阶段\n预占资源"];
SuccessPath [label="Try成功\n提交事务"];
FailPath [label="Try失败\n回滚事务"];
CancelTrigger [label="触发Cancel\n查询状态"];
CancelCheck [label="状态是否为\nTRY_PENDING?", shape=diamond];
CancelExecute [label="执行Cancel SQL\n恢复资源"];
UpdateStatus [label="更新状态为\nCANCELLED"];
ConfirmPath [label="后续Confirm\n(本图省略)"];
TryPhase -> SuccessPath;
TryPhase -> FailPath;
FailPath -> CancelTrigger;
CancelTrigger -> CancelCheck;
CancelCheck -> CancelExecute [label="是"];
CancelCheck -> ConfirmPath [label="否"];
CancelExecute -> UpdateStatus;
UpdateStatus -> End [label="Cancel完成", shape=doublecircle];
ConfirmPath -> EndConfirm [label="Confirm完成", shape=doublecircle];
}
<pre class="brush:php;toolbar:false;">digraph G {
rankdir=LR;
node [shape=record, fillcolor=white, fontsize=16];
ConfigNode [label="<f0> autoCommit | <f1> false"];
TxnControl [label="<f0> setAutoCommit() | <f1> 控制事务边界"];
CommitOp [label="<f0> commit() | <f1> 提交Try结果"];
RollbackOp [label="<f0> rollback() | <f1> 撤销Try操作"];
ConfigNode:f0 -> TxnControl:f0;
TxnControl:f1 -> CommitOp:f0;
TxnControl:f1 -> RollbackOp:f0;
}</f1></f0></f1></f0></f1></f0></f1></f0>


















