[GitHub] [shardingsphere] airship-lion commented on issue #7659: sharding-proxy integration seata error

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

airship-lion commented on issue #7659:
URL: https://github.com/apache/shardingsphere/issues/7659#issuecomment-701278598


   It runs normally now. I forgot to open the seata server before, but I found that when the transaction is started, if the program reports an error in the transaction, the branch transaction can be rolled back normally, but the program does not report an error in the transaction. I manually close a data source instance , The transactions of other data sources that are not closed cannot be rolled back normally. I do not need
   Shardingsphere, directly integrate seata with multiple data sources in the program. Under the same circumstances, the transactions of other data sources can be rolled back normally.
   ![sharding-proxy-test](https://user-images.githubusercontent.com/27192321/94668136-4416c580-0342-11eb-9d54-bd7e227898c1.png)
   ![sharding-proxy-service-1](https://user-images.githubusercontent.com/27192321/94668300-71637380-0342-11eb-860c-4db9c2672af9.png)
   ![sharding-proxy-service-2](https://user-images.githubusercontent.com/27192321/94668416-95bf5000-0342-11eb-8647-b24f852e8d9c.png)
   The above is the code for testing the proxy. When I ran, I interrupted at the end of the transaction, and then closed one of the data source instances
   
   The code for directly integrating seata is similar. It is also a single project with multiple data sources, and seata is configured in the direct project, but it can be rolled back normally.
   
   
   
   


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