[GitHub] [shardingsphere] git-chenhao opened a new issue, #18684: JDBCBackendConnection：proxy-db connection no rollback when application-proxy connection is closed

Tue, 28 Jun 2022 23:38:55 -0700 


git-chenhao opened a new issue, #18684:
URL: https://github.com/apache/shardingsphere/issues/18684

   ## Bug Report
   
   ### Which version of ShardingSphere did you use?
    5.1.0
   ### 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 no rollback(proxy-db) when connection ( application-proxy) is 
closed
   
   ### Reason analyze (If you can)
   
   
![image](https://user-images.githubusercontent.com/20919316/176368125-9b7c3595-f0f1-4534-bdcb-ff44acbcc4de.png)
   
   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, 
the resources in the JDBCBackendConnection are still empty. Because step 7 has 
not been started, the subsequent step 7 is executed after the resources are 
cleaned up, and the subsequent connection will remain there.
   
   


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

Reply via email to