【Java】Seata全局事务与本地事务的用法

已于 2023-02-06 23:46:13 修改
阅读量1.3k 收藏
点赞数
分类专栏： 学习时候记录的笔记 文章标签： java 数据库 seata
于 2023-02-06 23:18:09 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_41279172/article/details/128909970
版权

Seata全局事务与本地事务的用法

Seata安装教程

安装教程

AT模式相关

  1. 在数据库本地事务隔离级别是读已提交（Read Committed）或以上的基础上，AT模式的默认全局隔离级别是读未提交(Read Uncommitted)。如果必须要求全局的读已提交，目前seata的方式是通过select for update语句的代理。SELECT FOR UPDATE 语句的执行会查询全局锁，如果全局锁被其他事务持有，则释放本地锁（回滚 SELECT FOR UPDATE 语句的本地执行）并重试。这个过程中，查询是被 block 住的，直到全局锁拿到，即读取的相关数据是已提交的，才返回。

  2. AT 会对写操作的 SQL 进行拦截，提交本地事务前，会向 TC 获取全局锁，未获取到全局锁的情况下，不能进行写，以此来保证不会发生写冲突：

  • 一阶段本地事务提交前，需要确保先拿到全局锁；
  • 拿不到全局锁，不能提交本地事务；
  • 拿全局锁的尝试被限制在一定范围内，超出范围将放弃，并回滚本地事务，释放本地锁。

当只有全局事务，内部没有本地事务的情况

表结构sql:

-- auto-generated definition
create table student
(
    urid int auto_increment
        primary key,
    code varchar(255) null,
    name varchar(255) null
);

代码示例：

package cn.itcast.user.service.impl;

import cn.itcast.user.mapper.StudentMapper;
import cn.itcast.user.pojo.Student;
import cn.itcast.user.service.SeataTestService;
import io.seata.spring.annotation.GlobalTransactional;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.stereotype.Service;


@Service
public class SeataTestServiceImpl implements SeataTestService {

    @Autowired
    private StudentMapper studentMapper;

    @Override
    @GlobalTransactional
    public void withoutLocalTransaction() throws InterruptedException {
        Student student = new Student();
        student.setCode("103");
        student.setName("0206");
        studentMapper.insert(student);

        // 模拟中间的一些业务操作
        Thread.sleep(1000);

        Student studentInDB = studentMapper.getStudentByCode("103");
        System.out.println("此时数据库中的数据：" + studentInDB);
        studentInDB.setName("2311");
        studentMapper.updateById(studentInDB);
        // 模拟中间的一些业务操作
        Thread.sleep(1000);
        studentInDB = studentMapper.getStudentByCode("103");
        System.out.println("修改后数据库中的数据：" + studentInDB);
    }
}

另外使用了一个新的请求来模拟中间的查询调用：

在这里插入图片描述

最后的日志结果全文如下：

02-06 23:32:38:646 DEBUG 1800 --- [nio-8081-exec-3] .s.i.h.TransactionPropagationIntercepter : xid in RootContext[null] xid in HttpContext[null]
02-06 23:32:38:647 DEBUG 1800 --- [nio-8081-exec-3] i.s.c.r.n.AbstractNettyRemotingClient    : offer message: timeout=60000,transactionName=withoutLocalTransaction()
02-06 23:32:38:647 DEBUG 1800 --- [Send_TMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : write message:SeataMergeMessage timeout=60000,transactionName=withoutLocalTransaction()
, channel:[id: 0xad179dd9, L:/127.0.0.1:54807 - R:/127.0.0.1:8091],active?true,writable?true,isopen?true
02-06 23:32:38:651 DEBUG 1800 --- [ctor_TMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : io.seata.core.rpc.netty.TmNettyRemotingClient@8fc6ef9 msgId:42, body:MergeResultMessage xid=172.16.11.4:8091:366004859934097408;extraData=;

02-06 23:32:38:651 DEBUG 1800 --- [nio-8081-exec-3] io.seata.core.context.RootContext        : bind 172.16.11.4:8091:366004859934097408
02-06 23:32:38:651  INFO 1800 --- [nio-8081-exec-3] i.seata.tm.api.DefaultGlobalTransaction  : Begin new global transaction [172.16.11.4:8091:366004859934097408]
Creating a new SqlSession
SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@2f9479cf] was not registered for synchronization because synchronization is not active
JDBC Connection [io.seata.rm.datasource.ConnectionProxy@2153924d] will not be managed by Spring
==>  Preparing: INSERT INTO student ( code, name ) VALUES ( ?, ? )
==> Parameters: 106(String), 020600(String)
02-06 23:32:38:655 DEBUG 1800 --- [nio-8081-exec-3] i.s.c.r.n.AbstractNettyRemotingClient    : offer message: xid=172.16.11.4:8091:366004859934097408,branchType=AT,resourceId=jdbc:mysql://127.0.0.1:3306/gotest,lockKey=student:11
02-06 23:32:38:655 DEBUG 1800 --- [Send_RMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : write message:SeataMergeMessage xid=172.16.11.4:8091:366004859934097408,branchType=AT,resourceId=jdbc:mysql://127.0.0.1:3306/gotest,lockKey=student:11
, channel:[id: 0x0107a5c3, L:/127.0.0.1:52087 - R:/127.0.0.1:8091],active?true,writable?true,isopen?true
02-06 23:32:38:658 DEBUG 1800 --- [ctor_RMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : io.seata.core.rpc.netty.RmNettyRemotingClient@cee3f84 msgId:46, body:MergeResultMessage BranchRegisterResponse: branchId=366004859967651840,result code =Success,getMsg =null

02-06 23:32:38:659 DEBUG 1800 --- [nio-8081-exec-3] i.s.r.d.undo.AbstractUndoLogManager      : Flushing UNDO LOG: {"@class":"io.seata.rm.datasource.undo.BranchUndoLog","xid":"172.16.11.4:8091:366004859934097408","branchId":366004859967651840,"sqlUndoLogs":["java.util.ArrayList",[{"@class":"io.seata.rm.datasource.undo.SQLUndoLog","sqlType":"INSERT","tableName":"student","beforeImage":{"@class":"io.seata.rm.datasource.sql.struct.TableRecords$EmptyTableRecords","tableName":"student","rows":["java.util.ArrayList",[]]},"afterImage":{"@class":"io.seata.rm.datasource.sql.struct.TableRecords","tableName":"student","rows":["java.util.ArrayList",[{"@class":"io.seata.rm.datasource.sql.struct.Row","fields":["java.util.ArrayList",[{"@class":"io.seata.rm.datasource.sql.struct.Field","name":"urid","keyType":"PRIMARY_KEY","type":4,"value":11},{"@class":"io.seata.rm.datasource.sql.struct.Field","name":"code","keyType":"NULL","type":12,"value":"106"},{"@class":"io.seata.rm.datasource.sql.struct.Field","name":"name","keyType":"NULL","type":12,"value":"020600"}]]}]]}}]]}
<==    Updates: 1
Closing non transactional SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@2f9479cf]
02-06 23:32:41:257 DEBUG 1800 --- [nio-8081-exec-5] .s.i.h.TransactionPropagationIntercepter : xid in RootContext[null] xid in HttpContext[null]
Creating a new SqlSession
SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@4b70b320] was not registered for synchronization because synchronization is not active
JDBC Connection [io.seata.rm.datasource.ConnectionProxy@5cca8640] will not be managed by Spring
==>  Preparing: select * from student where code = 106
==> Parameters: 
<==    Columns: urid, code, name
<==        Row: 11, 106, 020600
<==      Total: 1
Closing non transactional SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@4b70b320]
Creating a new SqlSession
SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@14f8f0f8] was not registered for synchronization because synchronization is not active
JDBC Connection [io.seata.rm.datasource.ConnectionProxy@416739] will not be managed by Spring
==>  Preparing: select * from student where code = 106
==> Parameters: 
<==    Columns: urid, code, name
<==        Row: 11, 106, 020600
<==      Total: 1
Closing non transactional SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@14f8f0f8]
此时数据库中的数据：Student(urid=11, code=106, name=020600)
Creating a new SqlSession
SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@5cd009e2] was not registered for synchronization because synchronization is not active
JDBC Connection [io.seata.rm.datasource.ConnectionProxy@6de996f8] will not be managed by Spring
==>  Preparing: UPDATE student SET code=?, name=? WHERE urid=?
==> Parameters: 106(String), 2325(String), 11(Long)
02-06 23:32:43:733 DEBUG 1800 --- [nio-8081-exec-3] i.s.c.r.n.AbstractNettyRemotingClient    : offer message: xid=172.16.11.4:8091:366004859934097408,branchType=AT,resourceId=jdbc:mysql://127.0.0.1:3306/gotest,lockKey=student:11
02-06 23:32:43:733 DEBUG 1800 --- [Send_RMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : write message:SeataMergeMessage xid=172.16.11.4:8091:366004859934097408,branchType=AT,resourceId=jdbc:mysql://127.0.0.1:3306/gotest,lockKey=student:11
, channel:[id: 0x0107a5c3, L:/127.0.0.1:52087 - R:/127.0.0.1:8091],active?true,writable?true,isopen?true
02-06 23:32:43:735 DEBUG 1800 --- [ctor_RMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : io.seata.core.rpc.netty.RmNettyRemotingClient@cee3f84 msgId:48, body:MergeResultMessage BranchRegisterResponse: branchId=366004881262133248,result code =Success,getMsg =null

02-06 23:32:43:736 DEBUG 1800 --- [nio-8081-exec-3] i.s.r.d.undo.AbstractUndoLogManager      : Flushing UNDO LOG: {"@class":"io.seata.rm.datasource.undo.BranchUndoLog","xid":"172.16.11.4:8091:366004859934097408","branchId":366004881262133248,"sqlUndoLogs":["java.util.ArrayList",[{"@class":"io.seata.rm.datasource.undo.SQLUndoLog","sqlType":"UPDATE","tableName":"student","beforeImage":{"@class":"io.seata.rm.datasource.sql.struct.TableRecords","tableName":"student","rows":["java.util.ArrayList",[{"@class":"io.seata.rm.datasource.sql.struct.Row","fields":["java.util.ArrayList",[{"@class":"io.seata.rm.datasource.sql.struct.Field","name":"urid","keyType":"PRIMARY_KEY","type":4,"value":11},{"@class":"io.seata.rm.datasource.sql.struct.Field","name":"code","keyType":"NULL","type":12,"value":"106"},{"@class":"io.seata.rm.datasource.sql.struct.Field","name":"name","keyType":"NULL","type":12,"value":"020600"}]]}]]},"afterImage":{"@class":"io.seata.rm.datasource.sql.struct.TableRecords","tableName":"student","rows":["java.util.ArrayList",[{"@class":"io.seata.rm.datasource.sql.struct.Row","fields":["java.util.ArrayList",[{"@class":"io.seata.rm.datasource.sql.struct.Field","name":"urid","keyType":"PRIMARY_KEY","type":4,"value":11},{"@class":"io.seata.rm.datasource.sql.struct.Field","name":"code","keyType":"NULL","type":12,"value":"106"},{"@class":"io.seata.rm.datasource.sql.struct.Field","name":"name","keyType":"NULL","type":12,"value":"2325"}]]}]]}}]]}
<==    Updates: 1
Closing non transactional SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@5cd009e2]
02-06 23:32:46:808 DEBUG 1800 --- [nio-8081-exec-4] .s.i.h.TransactionPropagationIntercepter : xid in RootContext[null] xid in HttpContext[null]
Creating a new SqlSession
SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@1dc57973] was not registered for synchronization because synchronization is not active
JDBC Connection [io.seata.rm.datasource.ConnectionProxy@1b3aeffb] will not be managed by Spring
==>  Preparing: select * from student where code = 106
==> Parameters: 
<==    Columns: urid, code, name
<==        Row: 11, 106, 2325
<==      Total: 1
Closing non transactional SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@1dc57973]
02-06 23:32:48:658 DEBUG 1800 --- [ctor_TMROLE_1_1] i.s.c.r.n.AbstractNettyRemotingClient    : will send ping msg,channel [id: 0xad179dd9, L:/127.0.0.1:54807 - R:/127.0.0.1:8091]
02-06 23:32:48:658 DEBUG 1800 --- [ctor_TMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : write message:services ping, channel:[id: 0xad179dd9, L:/127.0.0.1:54807 - R:/127.0.0.1:8091],active?true,writable?true,isopen?true
02-06 23:32:48:659 DEBUG 1800 --- [ctor_TMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : io.seata.core.rpc.netty.TmNettyRemotingClient@8fc6ef9 msgId:43, body:services pong
02-06 23:32:48:659 DEBUG 1800 --- [ctor_TMROLE_1_1] i.s.c.r.p.c.ClientHeartbeatProcessor     : received PONG from /127.0.0.1:8091
Creating a new SqlSession
SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@614c4ad4] was not registered for synchronization because synchronization is not active
JDBC Connection [io.seata.rm.datasource.ConnectionProxy@2438f2e] will not be managed by Spring
==>  Preparing: select * from student where code = 106
==> Parameters: 
<==    Columns: urid, code, name
<==        Row: 11, 106, 2325
<==      Total: 1
Closing non transactional SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@614c4ad4]
修改后数据库中的数据：Student(urid=11, code=106, name=2325)
02-06 23:32:48:784 DEBUG 1800 --- [nio-8081-exec-3] i.s.c.r.n.AbstractNettyRemotingClient    : offer message: xid=172.16.11.4:8091:366004859934097408,extraData=null
02-06 23:32:48:784 DEBUG 1800 --- [Send_TMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : write message:SeataMergeMessage xid=172.16.11.4:8091:366004859934097408,extraData=null
, channel:[id: 0xad179dd9, L:/127.0.0.1:54807 - R:/127.0.0.1:8091],active?true,writable?true,isopen?true
02-06 23:32:48:786 DEBUG 1800 --- [ctor_TMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : io.seata.core.rpc.netty.TmNettyRemotingClient@8fc6ef9 msgId:45, body:MergeResultMessage globalStatus=Committed,ResultCode=Success,Msg=null

02-06 23:32:48:786 DEBUG 1800 --- [nio-8081-exec-3] io.seata.core.context.RootContext        : unbind 172.16.11.4:8091:366004859934097408 
02-06 23:32:48:786 DEBUG 1800 --- [nio-8081-exec-3] i.seata.tm.api.DefaultGlobalTransaction  : Suspending current transaction,xid = 172.16.11.4:8091:366004859934097408
02-06 23:32:48:786  INFO 1800 --- [nio-8081-exec-3] i.seata.tm.api.DefaultGlobalTransaction  : [172.16.11.4:8091:366004859934097408] commit status: Committed
02-06 23:32:48:789 DEBUG 1800 --- [nio-8081-exec-6] .s.i.h.TransactionPropagationIntercepter : xid in RootContext[null] xid in HttpContext[null]
02-06 23:32:48:791 DEBUG 1800 --- [nio-8081-exec-6] .s.i.h.TransactionPropagationIntercepter : xid in RootContext[null] xid in HttpContext[null]
02-06 23:32:49:077 DEBUG 1800 --- [ctor_RMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : io.seata.core.rpc.netty.RmNettyRemotingClient@cee3f84 msgId:10, body:xid=172.16.11.4:8091:366004859934097408,branchId=366004859967651840,branchType=AT,resourceId=jdbc:mysql://127.0.0.1:3306/gotest,applicationData=null
02-06 23:32:49:078  INFO 1800 --- [h_RMROLE_1_5_32] i.s.c.r.p.c.RmBranchCommitProcessor      : rm client handle branch commit process:xid=172.16.11.4:8091:366004859934097408,branchId=366004859967651840,branchType=AT,resourceId=jdbc:mysql://127.0.0.1:3306/gotest,applicationData=null
02-06 23:32:49:078  INFO 1800 --- [h_RMROLE_1_5_32] io.seata.rm.AbstractRMHandler            : Branch committing: 172.16.11.4:8091:366004859934097408 366004859967651840 jdbc:mysql://127.0.0.1:3306/gotest null
02-06 23:32:49:078  INFO 1800 --- [h_RMROLE_1_5_32] io.seata.rm.AbstractRMHandler            : Branch commit result: PhaseTwo_Committed
02-06 23:32:49:078 DEBUG 1800 --- [h_RMROLE_1_5_32] i.s.c.r.p.c.RmBranchCommitProcessor      : branch commit result:xid=172.16.11.4:8091:366004859934097408,branchId=366004859967651840,branchStatus=PhaseTwo_Committed,result code =Success,getMsg =null
02-06 23:32:49:078 DEBUG 1800 --- [h_RMROLE_1_5_32] i.s.c.rpc.netty.AbstractNettyRemoting    : write message:xid=172.16.11.4:8091:366004859934097408,branchId=366004859967651840,branchStatus=PhaseTwo_Committed,result code =Success,getMsg =null, channel:[id: 0x0107a5c3, L:/127.0.0.1:52087 - R:/127.0.0.1:8091],active?true,writable?true,isopen?true
02-06 23:32:49:079 DEBUG 1800 --- [ctor_RMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : io.seata.core.rpc.netty.RmNettyRemotingClient@cee3f84 msgId:11, body:xid=172.16.11.4:8091:366004859934097408,branchId=366004881262133248,branchType=AT,resourceId=jdbc:mysql://127.0.0.1:3306/gotest,applicationData=null
02-06 23:32:49:079  INFO 1800 --- [h_RMROLE_1_6_32] i.s.c.r.p.c.RmBranchCommitProcessor      : rm client handle branch commit process:xid=172.16.11.4:8091:366004859934097408,branchId=366004881262133248,branchType=AT,resourceId=jdbc:mysql://127.0.0.1:3306/gotest,applicationData=null
02-06 23:32:49:079  INFO 1800 --- [h_RMROLE_1_6_32] io.seata.rm.AbstractRMHandler            : Branch committing: 172.16.11.4:8091:366004859934097408 366004881262133248 jdbc:mysql://127.0.0.1:3306/gotest null
02-06 23:32:49:079  INFO 1800 --- [h_RMROLE_1_6_32] io.seata.rm.AbstractRMHandler            : Branch commit result: PhaseTwo_Committed
02-06 23:32:49:079 DEBUG 1800 --- [h_RMROLE_1_6_32] i.s.c.r.p.c.RmBranchCommitProcessor      : branch commit result:xid=172.16.11.4:8091:366004859934097408,branchId=366004881262133248,branchStatus=PhaseTwo_Committed,result code =Success,getMsg =null
02-06 23:32:49:079 DEBUG 1800 --- [h_RMROLE_1_6_32] i.s.c.rpc.netty.AbstractNettyRemoting    : write message:xid=172.16.11.4:8091:366004859934097408,branchId=366004881262133248,branchStatus=PhaseTwo_Committed,result code =Success,getMsg =null, channel:[id: 0x0107a5c3, L:/127.0.0.1:52087 - R:/127.0.0.1:8091],active?true,writable?true,isopen?true
02-06 23:32:49:823 DEBUG 1800 --- [AsyncWorker_1_1] i.s.r.d.undo.AbstractUndoLogManager      : batch delete undo log size 2
02-06 23:32:58:810 DEBUG 1800 --- [ctor_TMROLE_1_1] i.s.c.r.n.AbstractNettyRemotingClient    : will send ping msg,channel [id: 0xad179dd9, L:/127.0.0.1:54807 - R:/127.0.0.1:8091]
02-06 23:32:58:810 DEBUG 1800 --- [ctor_TMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : write message:services ping, channel:[id: 0xad179dd9, L:/127.0.0.1:54807 - R:/127.0.0.1:8091],active?true,writable?true,isopen?true
02-06 23:32:58:810 DEBUG 1800 --- [ctor_TMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : io.seata.core.rpc.netty.TmNettyRemotingClient@8fc6ef9 msgId:46, body:services pong
02-06 23:32:58:811 DEBUG 1800 --- [ctor_TMROLE_1_1] i.s.c.r.p.c.ClientHeartbeatProcessor     : received PONG from /127.0.0.1:8091
02-06 23:32:59:106 DEBUG 1800 --- [ctor_RMROLE_1_1] i.s.c.r.n.AbstractNettyRemotingClient    : will send ping msg,channel [id: 0x0107a5c3, L:/127.0.0.1:52087 - R:/127.0.0.1:8091]
02-06 23:32:59:106 DEBUG 1800 --- [ctor_RMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : write message:services ping, channel:[id: 0x0107a5c3, L:/127.0.0.1:52087 - R:/127.0.0.1:8091],active?true,writable?true,isopen?true
02-06 23:32:59:107 DEBUG 1800 --- [ctor_RMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : io.seata.core.rpc.netty.RmNettyRemotingClient@cee3f84 msgId:49, body:services pong
02-06 23:32:59:107 DEBUG 1800 --- [ctor_RMROLE_1_1] i.s.c.r.p.c.ClientHeartbeatProcessor     : received PONG from /127.0.0.1:8091
02-06 23:33:08:829 DEBUG 1800 --- [ctor_TMROLE_1_1] i.s.c.r.n.AbstractNettyRemotingClient    : will send ping msg,channel [id: 0xad179dd9, L:/127.0.0.1:54807 - R:/127.0.0.1:8091]
02-06 23:33:08:829 DEBUG 1800 --- [ctor_TMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : write message:services ping, channel:[id: 0xad179dd9, L:/127.0.0.1:54807 - R:/127.0.0.1:8091],active?true,writable?true,isopen?true
02-06 23:33:08:830 DEBUG 1800 --- [ctor_TMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : io.seata.core.rpc.netty.TmNettyRemotingClient@8fc6ef9 msgId:47, body:services pong
02-06 23:33:08:830 DEBUG 1800 --- [ctor_TMROLE_1_1] i.s.c.r.p.c.ClientHeartbeatProcessor     : received PONG from /127.0.0.1:8091
02-06 23:33:09:125 DEBUG 1800 --- [ctor_RMROLE_1_1] i.s.c.r.n.AbstractNettyRemotingClient    : will send ping msg,channel [id: 0x0107a5c3, L:/127.0.0.1:52087 - R:/127.0.0.1:8091]
02-06 23:33:09:125 DEBUG 1800 --- [ctor_RMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : write message:services ping, channel:[id: 0x0107a5c3, L:/127.0.0.1:52087 - R:/127.0.0.1:8091],active?true,writable?true,isopen?true
02-06 23:33:09:126 DEBUG 1800 --- [ctor_RMROLE_1_1] i.s.c.rpc.netty.AbstractNettyRemoting    : io.seata.core.rpc.netty.RmNettyRemotingClient@cee3f84 msgId:50, body:services pong
02-06 23:33:09:126 DEBUG 1800 --- [ctor_RMROLE_1_1] i.s.c.r.p.c.ClientHeartbeatProcessor     : received PONG from /127.0.0.1:8091

能够明显的看到当内部没有本地事务的时候每个数据库操作都会是一个事务。

在这里插入图片描述

且在全局事务提交之前能够读取到数据库更新后的内容。

在这里插入图片描述

当内部嵌入本地事务的情况

to be continue

wannatolive
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
seata分布式事务0.9.0
02-25
seata分布式事务0.9.0
分布式事务Seata介绍
04-06
分布式事务Seata介绍
Java微服务分布式事务框架seata
最新发布
Java 技术专栏，从入门到精通，熟悉企业级开发
03-18 1万+
本章节介绍微服务分布式项目中，使用的事务框架seata。官网：http://seata.io/zh-cn/Data
SpringBoot+Dubbo+Seata分布式事务实战详解
08-25
主要介绍了SpringBoot+Dubbo+Seata分布式事务实战详解，文中通过示例代码介绍的非常详细，对大家的学习或者工作具有一定的参考学习价值，需要的朋友们下面随着小编来一起学习学习吧
Java分布式事务Seata安装和使用，SpringCloud Seata分布式事务安装配置和使用
蕃薯耀的博客
05-10 2882
Java分布式事务Seata安装和使用，SpringCloud Seata分布式事务安装配置和使用 ================================ ©Copyright 蕃薯耀2021-05-10 https://blog.csdn.net/w995223851 一、Seata 是什么? 官方文档： https://seata.io/zh-cn/docs/overview/what-is-seata.html Seata 是一款开源的分布式事务解决方案，致...
（Java企业 / 公司项目）分布式事务Seata详解（含Seata+Nacos组合使用）（二）
全栈技术分享，项目分享，资料分享
01-14 519
配置nacos打开下载好的文件夹找到配置文件配置中心的文件名就是data-id接下来修改注册中心启动项目模块打开seata服务出现注册中心，接下来打开nacos查看命名空间，nacos的配置在前面的博客当中有可以查看怎么集成。访问nacos，显示的信息都是前面配置成功的信息注意这里的id需要和配置文件中的一致， group也需要一致下面的配置内容为AT模式会有一个全局锁，用于防止脏读，线程1的事务修改了库存，但还没提交事务，线程2读库存的时候，读的还是原来的库存。
java事物 commit失败,BUG - TCC 二阶段 commit 超时异常，发起方无法感知事务状态
weixin_30952479的博客
03-21 3098
[√] I have searched the issues of this repository and believe that this is not a duplicate.Ⅰ. Issue Description为了验证TransactionTemplate.java里红框多个操作在异常情况下的一致性：1、第四步commitTransaction(tx);会往tc发送GlobalComm...
Seata TCC 分支事务
贝克街的流浪猫
03-31 499
引言 前面，我们已经介绍了 Seata 的整体设计思想，接下来我们深入到其实现细节中，本文介绍 Seata 中 TCC 模式分支事务的实现。 TCC 模式 先简单介绍一个 Seata 中 TCC 的使用方式, 然后我们在顺着它的使用方式, 一点点深入其实现方案。 在 Seata TCC 模式中, 每个 RM 都需要将 TCC 接口以 RPC 的形式暴露出去, 同时向 TC 中注册, 告诉 TC 自己是某一 TCC 接口的提供方, 这样如果发生提交或者回滚时, TC 就知道该去找谁了。然后 TM 在进行 TC
Fescar - RM 全局事务提交回滚流程
weixin_33843409的博客
02-20 585
开篇  这篇文章的目的主要是讲解RM在接收TC的请求后执行全局分支事务提交（doBranchCommit）和全局分支事务回滚（doBranchRollback）的流程。  全局的分支事务提交过程和回滚过程也算RM处理流程中核心的一环，了解以后并结合之前讲解的本地事务提交流程就能够较好的理解整个过程了。 全局事务操作流程 整体流程 public clas...
分布式系列（一）SprintBoot集成Seata 2PC实现分布式事务
流浪的喵的博客
04-22 474
SprintBoot集成Seata 2PC实现分布式事务 文章目录SprintBoot集成Seata 2PC实现分布式事务1.2PC的原理1.1 2PC概念1.2 2PC第一阶段1.3 2PC第二阶段1.4 2PC异常处理1.5 2PC的缺点2.Seata的原理2.1Seata组成2.2 Seata事务处理流程2.3 Seata实现2PC与传统2PC差别3.SpringBoot集成Seata 我们的业务场景是Admin管理员记录日志、调用订单微服务发起一个订单、商品根据订单的数量减少相应的商品 管理员的日志
Spring-cloud-transaction 分布式事务
m0_56726104的博客
05-12 567
Spring-cloud-transaction 分布式事务 学习seata分布式事务管理AT模式的笔记：用到的组件分别是 springcloud-eureka-feign-mybatis-seata 参考及源码：https://github.com/seata/seata-samples/tree/master/springcloud-eureka-feign-mybatis-seata 引用：https://github.com/seata/seata-samples/blob/master/sp
基于Java+txlcn+seata的分布式事务实现案例源码.zip
02-21
基于Java+txlcn+seata的分布式事务实现案例源码.zip ## txlcn 测试步骤 ### 准备工作 - 启动 MySQL Redis - 创建数据库 tx-manager txlcn-a txlcn-b txlcn-c - 在库 tx-manager 中执行 t_tx_exception.sql 创建...
第十章Seata--分布式事务
01-27
10.1.1事务 事务指的就是一个操作单元，在这个操作单元中的所有操作最终要保持一致的行为，要么所有操作都成功，要么所有的...本地事物其实可以认为是数据库提供的事务机制。说到数据库事务就不得不说，数据库事务中的
java手动添加事务和全局事务
weixin_52197188的博客
07-22 2070
java手动添加事务和全局事务
Seata 之 @GlobalLock 是AT模式下隔离性保障神器之一【保熟】
BASK2312的博客
05-12 745
Seata AT模式下，如果服务A(服务接口或方法)参与全局事务，即在全局事务中作为一个分支事务，那么会在 TC 侧添加行锁记录，用于保障全局事务的隔离性。但还有另外一种情况，如果某个服务B从调用上下文上看，并未与其他服务一起协作，而是一个独立的逻辑，但与其他参与全局事务的服务都操控表C中的记录；这种情况下如没有处理好隔离性，会导致服务A无法完成二阶段回滚；如服务A在参与全局事务在一阶段修改了表C中的D记录服务B也修改了表C中的D记录。但服务A所参与的全局事务在二阶段决议要回滚，而服务A。
JAVA：探索分布式事务管理Seata应用实践
木头
09-06 336
探索分布式事务管理Seata应用实践
Seata 高性能 RPC 通信的实现- 巧用 reactor 模式
mxt51220的博客
04-03 422
线程数：50 ~ 500keepAlive：500 秒线程名字前缀： "ServerHandlerThread"队列长度： 500拒绝策略：CallerRunsPolicy()，饱和的情况下，调用者来执行该任务，即 Netty 的 I/O 线程//饱和的情况下，调用者来执行该任务，即Netty的IO线程和创建各自的线程池，配置并不相同。1）线程数：默认值是 cpu 核数 _ 2 ~ cpu 核数 _ 2keepAlive：Integer.MAX_VALUE 秒。
seata分布式事务与本地事务同时起作用
qq_53205955的博客
01-12 2954
seata分布式事务与本地事务同时起作用 1.seata配置生效之后 @Transactional(propagation = Propagation.REQUIRED, rollbackFor = Exception.class) 不起作用 因为seata实现分布式事务代理了数据源，所以不起作用了 想要实现本地事务起作用，需要在代理配置源的配置中加上 @Bean("txManager") public DataSourceTransactionManager txManager(DataSourc
分布式事务之Seata中间件原理及流程详细分析
沉默的夏虫
03-25 641
在分布式系统中，分布式事务是一个必须要解决的问题，目前使用较多的是最终一致性方案。自年初阿里开源了Fescar（目前更名为Seata）后，该项目受到了极大的关注度。Seata以高性能和零侵入的方式为目标解决微服务领域的分布式事务难题，目前正处于快速迭代中，近期小目标是生产可用的Mysql版本。关于Seata的总体介绍，可以查看官方WIKI获得更多更全面的内容介绍。 本文主要基于spring cl...
seata全局事务代码怎么用
05-11
在使用 Seata 进行全局事务管理时，通常需要进行以下步骤： 1. 引入 Seata 相关依赖 在项目的 pom.xml 文件中添加以下依赖： ```xml <groupId>io.seata <artifactId>seata-all <version>1.4.0 ``` 2. 配置 ...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值