incubator-seata
incubator-seata copied to clipboard
apache
:fire: Seata is an easy-to-use, high-performance, open source distributed transaction solution.
- [ ] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. ### Ⅰ. Issue Description 在执行新增操作的时候，上游服务发生异常，结果下游服务不能实现回滚，一直是回滚重试PhaseTwo_RollbackFailed_Retryable sharding version : 4.1.1 - JDK...
seata服务端1.5.2,客户端1.4.2,正常 seata服务端1.5.2,客户端1.5.2,服务端报错 Caused by: java.sql.SQLIntegrityConstraintViolationException: Duplicate entry 'jdbc:mysql://127.0.0.1:3306/financiallogic^^^logic_test_1^^^6827' for key 'lock_table.PRIMARY' 查看了下,数据源代理提交时,lock_table的row_key重复导致, 去掉主键约束发现row_key相同,xid相同,branch_id不相同 求解?
@GlobalTransactional和@Transactional注解同时使用时，在回滚时加入@Transactional注解得方法没有得到回滚，且lock_table表里得事务记录没有被删除
使用seata时，同时使用@GlobalTransactional和@Transactional注解，@GlobalTransactional注解在接口最外层方法，@Transactional注解在内层方法上，事务失败时，加入@Transactional注解得操作没有被回滚，且lock_table表中有数据没有被删除，导致再次执行同样得操作时出现异常.如下： Could not commit JDBC transaction; nested exception is io.seata.rm.datasource.exec.LockConflictException: get global lock fail, xid:10.244.15.4:8091:5557653063327397852, lockKeys:d_member_info:5086811;d_integral_inventory:42560184;d_integral_detail_record:7766197;d_integral_header:6552630
## Why you need it? Any plan to support `Tencent Polaris` registration center ? ## How it could be? The internal service governance is using Polaris registry, but in the...
The AbstractAutoProxyCreator's wrapIfNecessary method does not expect to be overridden by subclasses, whereas getAdvicesAndAdvisorsForBean and shouldSkip expect to be overridden by subclasses even more. The logic of SeataAutoDataSourceProxyCreator's override of...
## Why you need it? Currently, there are two ways to define a `StateMachine`. One is to use the designer, and the other is to directly write JSON. If users...
TCC防悬挂问题
 prepare阶段，插入tcc_fence_log和targetCallback.execute();在一个事务里，targetCallback.execute()如果有了异常，随后插入的tcc_fence_log也会回滚，然后在rollback方法里，从数据库查到的tcc_fence_log为null，就不会再走实际的回滚方法了
- [ ] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. ### Ⅰ. 场景 数据库表使用4个字段建立联合主键，4个字段分别是（id，limit_type，limit_id，user_id），业务发生异常后，事务回滚失败，抛出异常！ ### Ⅱ. 异常信息 异常日志： ERROR [,] io.seata.rm.datasource.DataSourceManager[61]...
- [ ] I have registered the PR [changes](../changes). ### Ⅰ. Describe what this PR did ### Ⅱ. Does this pull request fix one issue? ### Ⅲ. Why don't you...
io.seata.server.coordinator.DefaultCore#doGlobalRollback中的 globalSession.getSortedBranches()需要修复成globalSession.getReverseSortedBranches();（[这个已经在2.x中修复](https://github.com/apache/incubator-seata/issues/6120)） 我计划自己修复后，自己重新打镜像。 由于2.0.0中没有修复这个bug，我自己2.0.0的源码，修改这样代码。[使用教程中的命令](https://github.com/apache/incubator-seata/blob/v2.0.0/distribution/Dockerfile)打包，打出来的镜像与从镜像仓库拉下来的差别较大。 ``` 打包命令 1. mvn -Prelease-seata -Dmaven.test.skip=true clean install -U 2. cd distribution/target/seata-server-2.0.0/seata/ 3. docker build --no-cache --build-arg SEATA_VERSION=2.0.0 -t seata-server:2.0.0 . ``` 问题： 1、是我使用的打包的命令不对么？ 2、有其他办法在2.0.0中fix这个bug么？ 下面是镜像内的内容...
