Spring Cloud入门-Seata处理分布式事务问题(Hoxton版本)

used decimal(10,0) DEFAULT NULL COMMENT ‘已用余额’,

residue decimal(10,0) DEFAULT ‘0’ COMMENT ‘剩余可用额度’,

PRIMARY KEY (id)

) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8;

INSERT INTO seata-account.account (id, user_id, total, used, residue) VALUES (‘1’, ‘1’, ‘1000’, ‘0’, ‘1000’);

[](()创建日志回滚表

使用Seata还需要在每个数据库中创建日志表，建表sql在seata-server的/conf/db_undo_log.sql中。

[](()完整数据库示意图

[](()制造一个分布式事务问题

---

这里我们会创建三个服务，一个订单服务，一个库存服务，一个账户服务。当用户下单时，会在订单服务中创建一个订单，然后通过远程调用库存服务来扣减下单商品的库存，再通过远程调用账户服务来扣减用户账户里面的余额，最后在订单服务中修改订单状态为已完成。该操作跨越三个数据库，有两次远程调用，很明显会有分布式事务问题。

[](()客户端配置

---

对seata-order-service、seata-storage-service和seata-account-service三个seata的客户端进行配置，它们配置大致相同，我们下面以seata-order-service的配置为例；

修改application.yml文件，自定义事务组的名称；

spring:

application:

name: seata-order-service

cloud:

alibaba:

seata:

#自定义事务组名称需要与seata-server中的对应

tx-service-group: my_test_tx_group

添加并修改file.conf配置文件，主要是修改自定义事务组名称；

transport {

tcp udt unix-domain-socket

type = “TCP”

#NIO NATIVE

server = “NIO”

#enable heartbeat

heartbeat = true

#thread factory for netty

thread-factory {

boss-thread-prefix = “NettyBoss”

worker-thread-prefix = “NettyServerNIOWorker”

server-executor-thread-prefix = “NettyServerBizHandler”

share-boss-worker = false

client-selector-thread-prefix = “NettyClientSelector”

client-selector-thread-size = 1

client-worker-thread-prefix = “NettyClientWorkerThread”

netty boss thread size,will not be used for UDT

boss-thread-size = 1

#auto default pin or 8

worker-thread-size = 8

}

shutdown {

when destroy server, wait seconds

wait = 3

}

serialization = “seata”

compressor = “none”

}

service {

#vgroup->rgroup

vgroup_mapping.my_test_tx_group = “default”

#only support single node

default.grouplist = “127.0.0.1:8091”

#degrade current not support

enableDegrade = false

#disable

disable = false

#unit ms,s,m,h,d represents milliseconds, seconds, minutes, hours, days, default permanent

max.commit.retry.timeout = “-1”

max.rollback.retry.timeout = “-1”

disableGlobalTransaction = false

}

client {

async.commit.buffer.limit = 10000

lock {

retry.internal = 10

retry.times = 30

}

report.retry.count = 5

tm.commit.retry.count = 1

tm.rollback.retry.count = 1

}

transaction {

undo.data.validation = true

undo.log.serialization = “jackson”

undo.log.save.days = 7

#schedule delete expired undo_log in milliseconds

undo.log.delete.period = 86400000

undo.log.table = “undo_log”

}

support {

spring

spring {

auto proxy the DataSource bean

datasource.autoproxy = false

}

}

添加并修改registry.conf配置文件，主要是将注册中心改为nacos；

registry {

file 、nacos 、eureka、redis、zk

type = “nacos”

nacos {

serverAddr = “localhost:8848”

namespace = “”

cluster = “default”

}

eureka {

serviceUrl = “http://localhost:8761/eureka”

application = “default”

weight = “1”

}

redis {

serverAddr = “localhost:6381”

db = “0”

}

zk {

cluster = “default”

serverAddr = “127.0.0.1:2181”

session.timeout = 6000

connect.timeout = 2000

}

file {

name = “file.conf”

}

}

config {

file、nacos 、apollo、zk

type = “file”

nacos {

serverAddr = “localhost”

namespace = “”

cluster = “default”

}

apollo {

app.id = “fescar-server”

apollo.meta = “http://192.168.1.204:8801”

}

zk {

serverAddr = “127.0.0.1:2181”

session.timeout = 6000

connect.timeout = 2000

}

file {

name = “file.conf”

}

}

在启动类中取消数据源的自动创建：

@EnableFeignClients

@EnableDiscoveryClient

@MapperScan(basePackages = {“com.jourwon.springcloud.mapper”})

@SpringBootApplication(exclude = DataSourceAutoConfiguration.class)

public class SeataOrderServiceApplication {

public static void main(String[] args) {

SpringApplication.run(SeataOrderServiceApplication.class, args);

}

}

创建配置使用Seata对数据源进行代理：

@Configuration

public class DataSourceProxyConfig {

@Value("${mybatis.mapper-locations}")

private String mapperLocation 《一线大厂Java面试题解析+后端开发学习笔记+最新架构讲解视频+实战项目源码讲义》开源 s;

@Bean

@ConfigurationProperties(prefix = “spring.datasource”)

public DataSource druidDataSource(){

return new DruidDataSource();

}

@Bean

public DataSourceProxy dataSourceProxy(DataSource dataSource) {

return new DataSourceProxy(dataSource);

}

@Bean

public SqlSessionFactory sqlSessionFactoryBean(DataSourceProxy dataSourceProxy) throws Exception {

SqlSessionFactoryBean sqlSessionFactoryBean = new SqlSessionFactoryBean();

sqlSessionFactoryBean.setDataSource(dataSourceProxy);

sqlSessionFactoryBean.setMapperLocations(new PathMatchingResourcePatternResolver()

.getResources(mapperLocations));

sqlSessionFactoryBean.setTransactionFactory(new SpringManagedTransactionFactory());

return sqlSessionFactoryBean.getObject();

}

}

使用@GlobalTransactional注解开启分布式事务：

@Service

public class OrderServiceImpl implements OrderService {

private static final Logger LOGGER = LoggerFactory.getLogger(OrderServiceImpl.class);

@Autowired

private OrderMapper orderMapper;

@Autowired

private StorageService storageService;

@Autowired

private AccountService accountService;

/**

• 创建订单->调用库存服务扣减库存->调用账户服务扣减账户余额->修改订单状态

*/

@Override

@GlobalTransactional(name = “my-test-create-order”,rollbackFor = Exception.class)

public void create(Order order) {

LOGGER.info("------->下单开始");

//本应用创建订单

orderMapper.create(order);

//远程调用库存服务扣减库存

LOGGER.info("------->order-service中扣减库存开始");

storageService.decrease(order.getProductI Java开源项目【ali1024.coding.net/public/P7/Java/git】 d(),order.getCount());

LOGGER.info("------->order-service中扣减库存结束");

//远程调用账户服务扣减余额

LOGGER.info("------->order-service中扣减余额开始");

accountService.decrease(order.getUserId(),order.getMoney());

LOGGER.info("------->order-service中扣减余额结束");

//修改订单状态为已完成

LOGGER.info("------->order-service中修改订单状态开始");

orderMapper.update(order.getUserId(),0);

LOGGER.info("------->order-service中修改订单状态结束");

LOGGER.info("------->下单结束");

}

}

[](()分布式事务功能演示

---

运行seata-order-service、seata-storage-service和seata-account-service三个服务；

seata-server和上面三个服务启动成功后，nacos的服务列表如下：

seata-server控制台的界面如下：

数据库初始信息状态：

调用接口进行下单操作后查看数据库：[http://localhost:8180/order/create?userId=1&productId=1&count=10&money=100](()

返回信息

{“data”:null,“message”:“订单创建成功!”,“code”:200}

seata-order-service服务日志如下

2019-12-31 16:43:03.065 INFO 4848 — [nio-8180-exec-1] c.j.s.service.impl.OrderServiceImpl : ------->下单开始

2019-12-31 16:43:03.081 WARN 4848 — [nfigOperate_2_2] io.seata.config.FileConfiguration : Could not found property client.rm.report.retry.count, try to use default value instead.

2019-12-31 16:43:03.082 WARN 4848 — [nfigOperate_2_2] io.seata.config.FileConfiguration : Could not found property client.report.success.enable, try to use default value instead.

2019-12-31 16:43:03.082 WARN 4848 — [nfigOperate_2_2] io.seata.config.FileConfiguration : Could not found property client.rm.lock.retry.policy.branch-rollback-on-conflict, try to use default value instead.

2019-12-31 16:43:03.171 INFO 4848 — [nio-8180-exec-1] c.j.s.service.impl.OrderServiceImpl : ------->order-service中扣减库存开始

2019-12-31 16:43:03.611 INFO 4848 — [orage-service-1] c.netflix.config.ChainedDynamicProperty : Flipping property: seata-storage-service.ribbon.ActiveConnectionsLimit to use NEXT property: niws.loadbalancer.availabilityFilteringRule.activeConnectionsLimit = 2147483647

2019-12-31 16:43:03.639 INFO 4848 — [orage-service-1] c.netflix.loadbalancer.BaseLoadBalancer : Client: seata-storage-service instantiated a LoadBalancer: DynamicServerListLoadBalancer:{NFLoadBalancer:name=seata-storage-service,current list of Servers=[],Load balancer stats=Zone stats: {},Server stats: []}ServerList:null

2019-12-31 16:43:03.644 INFO 4848 — [orage-service-1] c.n.l.DynamicServerListLoadBalancer : Using serverListUpdater PollingServerListUpdater

2019-12-31 16:43:03.669 INFO 4848 — [orage-service-1] c.netflix.config.ChainedDynamicProperty : Flipping property: seata-storage-service.ribbon.ActiveConnectionsLimit to use NEXT property: niws.loadbalancer.availabilityFilteringRule.activeConnectionsLimit = 2147483647

2019-12-31 16:43:03.670 INFO 4848 — [orage-service-1] c.n.l.DynamicServerListLoadBalancer : DynamicServerListLoadBalancer for client seata-storage-service initialized: DynamicServerListLoadBalancer:{NFLoadBalancer:name=seata-storage-service,current list of Servers=[10.172.29.232:8181],Load balancer stats=Zone stats: {unknown=[Zone:unknown; Instance count:1; Active connections count: 0; Circuit breaker tripped count: 0; Active connections per server: 0.0;]

},Server stats: [[Server:10.172.29.232:8181; Zone:UNKNOWN; Total Requests:0; Successive connection failure:0; Total blackout seconds:0; Last connection made:Thu Jan 01 08:00:00 CST 1970; First connection made: Thu Jan 01 08:00:00 CST 1970; Active Connections:0; total failure count in last (1000) msecs:0; average resp time:0.0; 90 percentile resp time:0.0; 95 percentile resp time:0.0; min resp time:0.0; max resp time:0.0; stddev resp time:0.0]

]}ServerList:com.alibaba.cloud.nacos.ribbon.NacosServerList@438c717d

2019-12-31 16:43:03.919 INFO 4848 — [nio-8180-exec-1] c.j.s.service.impl.OrderServiceImpl : ------->order-service中扣减库存结束

2019-12-31 16:43:03.920 INFO 4848 — [nio-8180-exec-1] c.j.s.service.impl.OrderServiceImpl : ------->order-service中扣减余额开始

2019-12-31 16:43:03.958 INFO 4848 — [count-service-1] c.netflix.config.ChainedDynamicProperty : Flipping property: seata-account-service.ribbon.ActiveConnectionsLimit to use NEXT property: niws.loadbalancer.availabilityFilteringRule.activeConnectionsLimit = 2147483647

2019-12-31 16:43:03.959 INFO 4848 — [count-service-1] c.netflix.loadbalancer.BaseLoadBalancer : Client: seata-account-service instantiated a LoadBalancer: DynamicServerListLoadBalancer:{NFLoadBalancer:name=seata-account-service,current list of Servers=[],Load balancer stats=Zone stats: {},Server stats: []}ServerList:null

2019-12-31 16:43:03.960 INFO 4848 — [count-service-1] c.n.l.DynamicServerListLoadBalancer : Using serverListUpdater PollingServerListUpdater

2019-12-31 16:43:03.970 INFO 4848 — [count-service-1] c.netflix.config.ChainedDynamicProperty : Flipping property: seata-account-service.ribbon.ActiveConnectionsLimit to use NEXT property: niws.loadbalancer.availabilityFilteringRule.activeConnectionsLimit = 2147483647

2019-12-31 16:43:03.970 INFO 4848 — [count-service-1] c.n.l.DynamicServerListLoadBalancer : DynamicServerListLoadBalancer for client seata-account-service initialized: DynamicServerListLoadBalancer:{NFLoadBalancer:name=seata-account-service,current list of Servers=[10.172.29.232:8182],Load balancer stats=Zone stats: {unknown=[Zone:unknown; Instance count:1; Active connections count: 0; Circuit breaker tripped count: 0; Active connections per server: 0.0;]

},Server stats: [[Server:10.172.29.232:8182; Zone:UNKNOWN; Total Requests:0; Successive connection failure:0; Total blackout seconds:0; Last connection made:Thu Jan 01 08:00:00 CST 1970; First connection made: Thu Jan 01 08:00:00 CST 1970; Active Connections:0; total failure count in last (1000) msecs:0; average resp time:0.0; 90 percentile resp time:0.0; 95 percentile resp time:0.0; min resp time:0.0; max resp time:0.0; stddev resp time:0.0]

]}ServerList:com.alibaba.cloud.nacos.ribbon.NacosServerList@2be5bb61

2019-12-31 16:43:03.988 INFO 4848 — [nio-8180-exec-1] c.j.s.service.impl.OrderServiceImpl : ------->order-service中扣减余额结束

2019-12-31 16:43:03.988 INFO 4848 — [nio-8180-exec-1] c.j.s.service.impl.OrderServiceImpl : ------->order-service中修改订单状态开始

2019-12-31 16:43:03.992 INFO 4848 — [nio-8180-exec-1] c.j.s.service.impl.OrderServiceImpl : ------->order-service中修改订单状态结束

2019-12-31 16:43:03.992 INFO 4848 — [nio-8180-exec-1] c.j.s.service.impl.OrderServiceImpl : ------->下单结束

我们在seata-account-service中制造一个超时异常后，调用下单接口：

@Service

public class AccountServiceImpl implements AccountService {

最后

ActiveMQ消息中间件面试专题

• 什么是ActiveMQ?
• ActiveMQ服务器宕机怎么办？
• 丢消息怎么办？
• 持久化消息非常慢怎么办？
• 消息的不均匀消费怎么办？
• 死信队列怎么办？
• ActiveMQ中的消息重发时间间隔和重发次数吗？

ActiveMQ消息中间件面试专题解析拓展：

---

redis面试专题及答案

• 支持一致性哈希的客户端有哪些？
• Redis与其他key-value存储有什么不同？
• Redis的内存占用情况怎么样？
• 都有哪些办法可以降低Redis的内存使用情况呢？
• 查看Redis使用情况及状态信息用什么命令？
• Redis的内存用完了会发生什么？
• Redis是单线程的，如何提高多核CPU的利用率？

---

Spring面试专题及答案

• 谈谈你对 Spring 的理解
• Spring 有哪些优点？
• Spring 中的设计模式
• 怎样开启注解装配以及常用注解
• 简单介绍下 Spring bean 的生命周期

Spring面试答案解析拓展

---

高并发多线程面试专题

• 现在有线程 T1、T2 和 T3。你如何确保 T2 线程在 T1 之后执行，并且 T3 线程在 T2 之后执行？
• Java 中新的 Lock 接口相对于同步代码块（synchronized block）有什么优势？如果让你实现一个高性能缓存，支持并发读取和单一写入，你如何保证数据完整性。
• Java 中 wait 和 sleep 方法有什么区别？
• 如何在 Java 中实现一个阻塞队列？
• 如何在 Java 中编写代码解决生产者消费者问题？
• 写一段死锁代码。你在 Java 中如何解决死锁？

高并发多线程面试解析与拓展

---

jvm面试专题与解析

• JVM 由哪些部分组成？
• JVM 内存划分？
• Java 的内存模型?
• 引用的分类？
• GC什么时候开始？

JVM面试专题解析与拓展！

)]

---

Spring面试专题及答案

• 谈谈你对 Spring 的理解
• Spring 有哪些优点？
• Spring 中的设计模式
• 怎样开启注解装配以及常用注解
• 简单介绍下 Spring bean 的生命周期

Spring面试答案解析拓展

[外链图片转存中…(img-3vB74ELb-1650349873953)]

---

高并发多线程面试专题

• 现在有线程 T1、T2 和 T3。你如何确保 T2 线程在 T1 之后执行，并且 T3 线程在 T2 之后执行？
• Java 中新的 Lock 接口相对于同步代码块（synchronized block）有什么优势？如果让你实现一个高性能缓存，支持并发读取和单一写入，你如何保证数据完整性。
• Java 中 wait 和 sleep 方法有什么区别？
• 如何在 Java 中实现一个阻塞队列？
• 如何在 Java 中编写代码解决生产者消费者问题？
• 写一段死锁代码。你在 Java 中如何解决死锁？

高并发多线程面试解析与拓展

[外链图片转存中…(img-wYJi9GWJ-1650349873954)]

---

jvm面试专题与解析

• JVM 由哪些部分组成？
• JVM 内存划分？
• Java 的内存模型?
• 引用的分类？
• GC什么时候开始？

JVM面试专题解析与拓展！

[外链图片转存中…(img-xCogNVvh-1650349873954)]