Self-revolution

使用seata操作MySQL，两个行锁不同的事务发生死锁问题

9

- [x] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. ### Ⅰ. Issue Description 使用seata 1.8.0操作MySQL，在更新数据前使用ID获取行锁。两个并发事务在同一个方法中通过ID获取行锁，且ID不同，并对该方法使用了@GlobalLock+@Transactional(rollbackFor = Exception.class)注解，且服务调用方还使用了@GlobalTransactional注解，结果不知为什么发生死锁。通过MySQL命令SHOW ENGINE INNODB STATUS 查看死锁日志，发生死锁的SQL似乎是@GlobalLock注解自动执行的：...

The AdapterSpringSeataInterceptor's order '2147483647' is lower or equals than TransactionInterceptor's order '2147483647' , reset AdapterSpringSeataInterceptor's order to higher order '2147483646'.

14

WARN i.s.s.annotation.GlobalTransactionScanner: The AdapterSpringSeataInterceptor's order '2147483647' is lower or equals than TransactionInterceptor's order '2147483647' , reset AdapterSpringSeataInterceptor's order to higher order '2147483646'. The warning appeared when I upgrade to seata...

seata2.1.0全局事务提交后，全局锁一直不释放

5

线上偶发`seata2.1.0.jre17`全局事务提交后，全局锁一直不释放，服务端报错`Global lock on [transport_task:1212475] is holding by 5576031298779548712`，但事务已提交`Committing global transaction is successfully done, xid = 192.168.12.222:8091:5576031298779548712.`： seata服务端日志如下，： ``` 2024-10-18 18:23:01.987 INFO --- [batchLoggerPrint_1_1] [org.apache.seata.core.rpc.processor.server.BatchLogHandler] [run] []: receive msg[single]: GlobalBeginRequest{transactionName='insertTask(com.holo.storage.service.container.vo.ContainerVO, com.holo.storage.service.locator.vo.LocatorVO,...