Re: [I] TCC模式怎么通过纯api方式使用呢？ [incubator-seata]

funky-eyes commented on issue #4828: URL: https://github.com/apache/incubator-seata/issues/4828#issuecomment-2229858721 https://seata.apache.org/docs/user/api -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL ab

Re: [I] TCC模式下，开启它的useTCCFence功能，mysql事务隔离级别是RR，如果prepare阶段发生悬挂 && rollback阶段也发生悬挂，会出现异常【Deadlock found when trying to get lock; try restarting transaction】 [incubator-seata]

funky-eyes commented on issue #6679: URL: https://github.com/apache/incubator-seata/issues/6679#issuecomment-2229820512 我认为这是出现了资源悬挂并且隔离级别为RR才会出现，故我们应该根据这两者制定解决方案： 1.由于这本身是资源悬挂，悬挂的资源最终是要进行回滚的，所以这类异常我们应该catch住，包装为seata的统一异常，告知用户可忽略此类异常，由于tc本身存在rollback重试机制，所以只需要提示用户即可。 2.我们可以结合spring的

Re: [I] Deadlock found when trying to get lock; try restarting transaction [incubator-seata]

funky-eyes commented on issue #3587: URL: https://github.com/apache/incubator-seata/issues/3587#issuecomment-2229792069 > > > 我们目前也出现这个问题。查看死锁信息发现是在 MySQL RR 事务隔离级别下。 > > > delete 语句是索引查询需要加了间隙锁并等待next key， > > > insert 加了行锁并等待间隙锁 。然后造成死锁。 > > > 这种情况只在高并发的时候才会出现 > > > 现在感觉可以简单的把事

Re: [I] Deadlock found when trying to get lock; try restarting transaction [incubator-seata]

funky-eyes closed issue #3587: Deadlock found when trying to get lock; try restarting transaction URL: https://github.com/apache/incubator-seata/issues/3587 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to

Re: [I] 使用seata操作MySQL，两个行锁不同的事务发生死锁问题 [incubator-seata]

funky-eyes commented on issue #6289: URL: https://github.com/apache/incubator-seata/issues/6289#issuecomment-2229785397 > 我通过执行MySQL的分析表命令修复了索引错误，解决了死锁问题。 对于`mysql release save point error`异常这个问题，通过日志可以看出，调用链是很清晰的，我确定没有上层的本地事务。我之前也没有遇到过这个报错信息，我怀疑会不会和`org.springframework.dao.DeadlockLoserDat

Re: [I] GlobalTransactionScanner 多例bean问题 [incubator-seata]

tanyaofei commented on issue #6568: URL: https://github.com/apache/incubator-seata/issues/6568#issuecomment-2229783999 > > > > > In my opinion, this code is just to avoid duplicate proxies. @wangliang181230 , @slievrly , @xingfudeshi , please help to answer this question. > > > > >

Re: [I] Oracle 11g数据库，使用Mybatisplus的saveBatch方法报错，提示违反协议 [incubator-seata]

Theodore1965 closed issue #6662: Oracle 11g数据库，使用Mybatisplus的saveBatch方法报错，提示违反协议 URL: https://github.com/apache/incubator-seata/issues/6662 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the speci

Re: [I] Oracle 11g数据库，使用Mybatisplus的saveBatch方法报错，提示违反协议 [incubator-seata]

Theodore1965 commented on issue #6662: URL: https://github.com/apache/incubator-seata/issues/6662#issuecomment-2229744385 更换jdbc驱动，ojdbc8版本号19.3.0.0解决该问题， 新异常信息为java.sql.SQLException: 关闭的语句， 修改druid配置poolPreparedStatements=false解决问题 -- This is an automated message from the Apache Gi

[I] TCC模式下，mysql事务隔离级别是RR，如果prepare阶段发生悬挂 && rollback阶段也发生悬挂，会出现异常【Deadlock found when trying to get lock; try restarting transaction】 [incubator-seata]

iAmClever opened a new issue, #6679: URL: https://github.com/apache/incubator-seata/issues/6679 ### Ⅰ. Issue Description TCC模式下，mysql事务隔离级别是RR，如果prepare阶段发生悬挂 && rollback阶段也发生悬挂，会出现异常【Deadlock found when trying to get lock; try restarting transaction】 ### Ⅱ. Describe what happened

Re: [PR] bugfix: fix the failure of rollbacking back of the delete SQL at AT m… [incubator-seata]

TakeActionNow2019 commented on code in PR #6511: URL: https://github.com/apache/incubator-seata/pull/6511#discussion_r1678020576 ## rm-datasource/src/main/java/org/apache/seata/rm/datasource/undo/sqlserver/SqlServerUndoDeleteExecutor.java: ## @@ -59,17 +71,75 @@ protected String

Re: [PR] tcc samples update [incubator-seata-website]

funky-eyes merged PR #873: URL: https://github.com/apache/incubator-seata-website/pull/873 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications

(incubator-seata-website) branch docusaurus updated: tcc samples update (#873)

This is an automated email from the ASF dual-hosted git repository. jianbin pushed a commit to branch docusaurus in repository https://gitbox.apache.org/repos/asf/incubator-seata-website.git The following commit(s) were added to refs/heads/docusaurus by this push: new 6152782e23 tcc samples

Re: [PR] Bugfix: Fixed that the same record has different lowkeys due to mixed case of table names [incubator-seata]

codecov[bot] commented on PR #6678: URL: https://github.com/apache/incubator-seata/pull/6678#issuecomment-2228559450 ## [Codecov](https://app.codecov.io/gh/apache/incubator-seata/pull/6678?dropdown=coverage&src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=p

[PR] Bugfix: Fixed that the same record has different lowkeys due to mixed case of table names [incubator-seata]

GoodBoyCoder opened a new pull request, #6678: URL: https://github.com/apache/incubator-seata/pull/6678 - [ ] I have registered the PR [changes](../changes). ### Ⅰ. Describe what this PR did When the database is case-insensitive, if different services use table names with d

[PR] tcc samples update [incubator-seata-website]

sunrui1225 opened a new pull request, #873: URL: https://github.com/apache/incubator-seata-website/pull/873 ## What is the purpose of the change X ## Brief changelog X Follow this checklist to help us incorporate your contribution quickly and easily: