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 2022/09/26 11:37:36 UTC

[GitHub] [shardingsphere] natehuangting opened a new issue, #21202: There is a deadlock problem in acquiring the connection

natehuangting opened a new issue, #21202:
URL: https://github.com/apache/shardingsphere/issues/21202

   ## Bug Report
   
   Assume that the logical table t_order corresponds to ds_${0..1}.t_order. The maximum number of connections for both ds_0 and ds_1 is 1. Request 1 has obtained the connection of ds_0, and is ready to request the connection of ds_1. Request 2 has obtained the connection of ds_1, and prepare to acquire the connection of ds_0. This is deadlock
   
   ### Which version of ShardingSphere did you use?
   master
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-Proxy


-- 
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: notifications-unsubscribe@shardingsphere.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] TeslaCN commented on issue #21202: There is a deadlock problem in acquiring the connection

Posted by GitBox <gi...@apache.org>.
TeslaCN commented on issue #21202:
URL: https://github.com/apache/shardingsphere/issues/21202#issuecomment-1263332011

   @tuichenchuxin I don't think this is a bug. It could be an enhancement.


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org