[CONJ-1002] Drive reconnect ignores default database/schema setting Created: 2022-08-24 Updated: 2022-09-02 Resolved: 2022-09-02 |
|
| Status: | Closed |
| Project: | MariaDB Connector/J |
| Component/s: | Failover |
| Affects Version/s: | 3.0.6 |
| Fix Version/s: | 3.0.8 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Pavel Cibulka | Assignee: | Diego Dupin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Ubuntu 20.04, Mariadb 10.6.9, Galera Cluster - 3 nodes, Apache Tomcat + Tomcat JDBC Connection Pool, OpenJDK 18.0.2 |
||
| Description |
|
I have following connection settings in tomcat's server.xml:
There is default database / schema settings - defaultCatalog="necy". This is sometimes ignored by j/connector. First I have error (this is as it should be): It seems driver somehow reconnects but without setting default database because I have ful log of following errors: java.util.concurrent.CompletionException: java.lang.InterruptedException: (conn=31) No database selected I think it is j/connector bug because error message come from MultiPrimaryClient.java file. |
| Comments |
| Comment by Diego Dupin [ 2022-09-02 ] |
|
There is one possible issue, that occurs on second reconnection when setting database using Connection.setCatalog() (that the case with your configuration). |