linghengqian commented on issue #34418:
URL:
https://github.com/apache/shardingsphere/issues/34418#issuecomment-2614010105
- From my point of view it is expected behavior for `CONNECTION_STRICTLY`
connection mode. The unit test correctly asserts this error.
```shell
Error:
org.apache.shardingsphere.driver.jdbc.core.connection.DriverDatabaseConnectionManagerTest.assertGetConnectionsWhenConnectionCreateFailed
-- Time elapsed: 0.008 s <<< FAILURE!
java.lang.AssertionError:
Expected: is "Can not get 3 connections one time, partition succeed
connection(0) have released. Please consider increasing the 'maxPoolSize' of
the data sources or decreasing the 'max-connections-size-per-query' in
properties.\nMore details: java.sql.SQLException: Mock invalid data source"
but: was "Mock invalid data source"
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6)
at
org.apache.shardingsphere.driver.jdbc.core.connection.DriverDatabaseConnectionManagerTest.assertGetConnectionsWhenConnectionCreateFailed(DriverDatabaseConnectionManagerTest.java:161)
at java.lang.reflect.Method.invoke(Method.java:498)
at java.util.ArrayList.forEach(ArrayList.java:1259)
at java.util.ArrayList.forEach(ArrayList.java:1259)
```
--
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]
