git-chenhao opened a new issue, #18734: URL: https://github.com/apache/shardingsphere/issues/18734
## Bug Report ### Which version of ShardingSphere did you use? master ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-Proxy ### Expected behavior transaction rollback(proxy-db) when connection ( application-proxy) is closed ### Actual behavior transaction commit(proxy-db) when connection ( application-proxy) is closed，This will result in inconsistent data  ### Reason analyze (If you can) When the above figure is executed to step 4-6, the disconnection of the upstream connection triggers the channelInactive method of Netty. At this time, JDBCBackendConnection will clear connectionPostProcessors <img width="809" alt="image" src="https://user-images.githubusercontent.com/20919316/176641343-ad682ac5-c4a6-4ae8-864b-d92fd7501ad4.png";> So, step 2 the stored a will be deleted. This causes the transaction to be automatically committed after step 10 is completed，Not as expected rollback！ ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. ### Example codes for reproduce this issue (such as a github link). -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
![https://user-images.githubusercontent.com/20919316/176641343-ad682ac5-c4a6-4ae8-864b-d92fd7501ad4.png"](https://user-images.githubusercontent.com/20919316/176641343-ad682ac5-c4a6-4ae8-864b-d92fd7501ad4.png"){kind=link}