You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2019/08/14 02:24:51 UTC

[GitHub] [incubator-shardingsphere] liuyangming commented on issue #2854: modify the enlistment to support the transaction propagation REQUIRES_NEW

liuyangming commented on issue #2854: modify the enlistment to support the transaction propagation REQUIRES_NEW
URL: https://github.com/apache/incubator-shardingsphere/pull/2854#issuecomment-521077760
 
 
   > I have understood the nested transaction issue.
   > but for XA TM implement (such as atomikos), they don't support enlist same resource multiple times in one XA transaction. you should make sure the modification runnable in our transaction-example at first.
   
   This scenario involves two XA transactions, not just one, but both XA transactions need to access the same resource. Since the transaction propagation level of the second transaction is REQUIRES_NEW, it requiures the TM performs the suspend/resume operation on the XAResource. 
   
   TM like Atomikos support suspend/resume operation, but currently mysql/postgresql as an RM does not supported (include join), other databases such as oracle and db2 are supported, the database h2 used in my current test case also supports too.
   
   The sample provided by shardingsphere is not a typical usage of a spring declarative transaction, so I created a new sample project based on this, hope can help to reproduce this problem. 
   
   github: ([https://github.com/liuyangming/shardingjdbc-sample](https://github.com/liuyangming/shardingjdbc-sample))

----------------------------------------------------------------
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