[GitHub] [incubator-shardingsphere] jimmycheng888 opened a new issue #2482: Introducing the transaction manager leads to conflict with the tcc-transaction framework

[GitBox <gi...@apache.org>]

jimmycheng888 opened a new issue #2482: Introducing the transaction manager leads to conflict with the tcc-transaction framework
URL: https://github.com/apache/incubator-shardingsphere/issues/2482
 
 
   **Which version of ShardingSphere did you use?**
   3.1.0
   
   **Which project did you use? Sharding-JDBC or Sharding-Proxy?**
   Sharding-JDBC
   
   **Actual behavior**
   The introduction of the transaction manager leads to a conflict with the tcc-transaction framework, because after the exception occurs, the jdbc transaction of tcc-transaction is managed by the shardingsphere, and from a business perspective, the business transaction and the log transaction should be separated. This will cause my tcc transaction log to be lost during the try phase, because I have an abnormal behavior during the try phase. Since shardingsphere is a distributed component, I hope that shardingsphere can be compatible with more middleware.
   
   ### Example codes for reproduce this issue (such as a github link).
   java Code
   
       **@Transactional(value = "dataSourceTransactionManager", rollbackFor = Exception.class)
       @Compensable(confirmMethod = "confirmIssue", cancelMethod = "cancelIssue")**
   
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services