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 2020/11/18 07:42:28 UTC
[GitHub] [shardingsphere] ben905713861 opened a new issue #8200: XA transaction in ShardingSphere-Proxy-5.0.0 is invalid
ben905713861 opened a new issue #8200:
URL: https://github.com/apache/shardingsphere/issues/8200
### Which version of ShardingSphere did you use?
5.0.0-alpha
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
### Expected behavior
I use XA transaction configuation, but the sharding-proxy does not send XA SQL to the physics node, the XA transaction is invalid.
```
props:
# # LOCAL: Proxy will run with LOCAL transaction.
# # XA: Proxy will run with XA transaction.
# # BASE: Proxy will run with B.A.S.E transaction.
proxy-transaction-type: XA
```
I write the SQL in sharding-proxy mysql client,the SQL is:
```sql
start transaction;
update activity set startTime="2020-08-01 18:00:01" where activityId=30;
rollback;
```
The result is change, transaction does not rollback.
### Actual behavior
This is my Wireshark analysis chart:
```
H update activity set startTime="2020-08-01 18:00:01" where activityId=300 (Rows matched: 1 Changed: 0 Warnings: 0
```
I can't see any XA SQL in the analysis.So I think the XA configuration is invalid.
----------------------------------------------------------------
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
[GitHub] [shardingsphere] kimmking closed issue #8200: XA transaction in ShardingSphere-Proxy-5.0.0 is invalid
Posted by GitBox <gi...@apache.org>.
kimmking closed issue #8200:
URL: https://github.com/apache/shardingsphere/issues/8200
----------------------------------------------------------------
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
[GitHub] [shardingsphere] kimmking edited a comment on issue #8200: XA transaction in ShardingSphere-Proxy-5.0.0 is invalid
Posted by GitBox <gi...@apache.org>.
kimmking edited a comment on issue #8200:
URL: https://github.com/apache/shardingsphere/issues/8200#issuecomment-729511063
duplicated with https://github.com/apache/shardingsphere/issues/8178
It has been fixed in master branch by @yu199195
you can try this branch or next release version.
----------------------------------------------------------------
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
[GitHub] [shardingsphere] kimmking edited a comment on issue #8200: XA transaction in ShardingSphere-Proxy-5.0.0 is invalid
Posted by GitBox <gi...@apache.org>.
kimmking edited a comment on issue #8200:
URL: https://github.com/apache/shardingsphere/issues/8200#issuecomment-729511063
duplicated with https://github.com/apache/shardingsphere/issues/8178
It has been fixed in master branch by @yu199195
----------------------------------------------------------------
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
[GitHub] [shardingsphere] kimmking commented on issue #8200: XA transaction in ShardingSphere-Proxy-5.0.0 is invalid
Posted by GitBox <gi...@apache.org>.
kimmking commented on issue #8200:
URL: https://github.com/apache/shardingsphere/issues/8200#issuecomment-729511063
duplicated with https://github.com/apache/shardingsphere/issues/8178
@yu199195 It has been fixed in master branch.
----------------------------------------------------------------
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