概览
seata client跟维持了一个连接,监听server端的消息,根据接到的消息判断是提交还是回滚。
客户端建立流程:
GlobalTransactionScanner.afterPropertiesSet()
GlobalTransactionScanner.initClient()
TMClient.init
TmRpcClient.getInstance
new TmRpcClient
new RpcClientBootstrap
RpcClientBootstrap内部包装了netty的Bootstrap,其中会向Bootstrap绑定一个ClientHandler用来处理seata server返回来的消息
,最终通过Bootstrap建立与server端的连接。
接下来就是核心处理逻辑了,先看看类图
这里ClientHandler实现了ChannelInboundHandler的channelRead()方法,netty在接收到消息(读事件)后,最终会调用channelRead,并传入读到的消息,具体细节可参考netty源码,所以,我们先来看下这个方法的执行流程
ClientHandler.channelRead
AbstractHandler.channelRead
ClientHandler.dispatch
RmMessageListener.onMessage
RmMessageListener会根据消息反序列化后的类型决定事物的提交与回滚
@Override
public void onMessage(RpcMessage request, String serverAddress) {
Object msg = request.getBody();
if (LOGGER.isInfoEnabled()) {
LOGGER.info("onMessage:" + msg);
}
if (msg instanceof BranchCommitRequest) {
handleBranchCommit(request, serverAddress, (BranchCommitRequest)msg);
} else if (msg instanceof BranchRollbackRequest) {
handleBranchRollback(request, serverAddress, (BranchRollbackRequest)msg);
} else if (msg instanceof UndoLogDeleteRequest) {
handleUndoLogDelete((UndoLogDeleteRequest) msg);
}
}
这里只说一下rollback,上面的rollback最终会到达AbstracRMHandler.doBranchRollback()
protected void doBranchRollback(BranchRollbackRequest request, BranchRollbackResponse response)
throws Tra