JiekerTime opened a new issue #11611:
URL: https://github.com/apache/shardingsphere/issues/11611


   The problem occurred with integration testing, which could not be resolved 
due to limited capabilities.
   
   ### Which version of ShardingSphere did you use?
   5.0.0-RC1-SNAPSHOT
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-JDBC 
   
   ### behavior
   
![image](https://user-images.githubusercontent.com/76552510/127949473-af3c8087-b0f8-4811-a2be-bc80e14fc467.png)
   
   ### Reason analyze (If you can)
   Dialect differences between PGSQL and MySQL result in Atomikos connections 
not being recycled.
   Or there may also likely the result of concurrency issues.
   But it works normally in MySQL scenarios.
   
![image](https://user-images.githubusercontent.com/76552510/127949775-1317aca2-059f-4c3e-a76e-4c2d0d820862.png)
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   Just create the data source concurrently by the following way:
   
![image](https://user-images.githubusercontent.com/76552510/127950118-43fd6da6-ca77-4d09-84ab-8ce5ace300db.png)
   You may wish to refer to the [integration testing 
framework](https://github.com/apache/shardingsphere/blob/master/shardingsphere-test/shardingsphere-integration-test/shardingsphere-integration-test-fixture/src/test/java/org/apache/shardingsphere/test/integration/junit/container/adapter/impl/ShardingSphereJDBCContainer.java)
   


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