https://bz.apache.org/bugzilla/show_bug.cgi?id=69395
Bug ID: 69395
Summary: Empty JDBC URI when using a jdbc connection pool
Product: Tomcat 9
Version: 9.0.96
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: -----
Hello,
I noticed that the same war behaves differently on the latest tomcat versions
(9.0.95/9.0.96).
The webapp works until a certain point (usually few minutes after the deploy)
and ends up with: Empty JDBC URI
but it's technically not possible because he know the JDBC URI at boot time and
the application is able to retrieve the info on mariadb server.
We are using a connection pool declared in this way:
<Resource name="jdbc/qm" auth="Container" type="javax.sql.DataSource"
username="user" password="pass" driverClassName="org.mariadb.jdbc.Driver"
url="jdbc:mariadb://127.0.0.1/db?sessionVariables=sql_mode=''&autoReconnect=true"
maxTotal="1000" maxIdle="5" validationQuery="SELECT 1" testOnBorrow="true"
timeBetweenEvictionRunsMillis="10000" minEvictableIdleTimeMillis="60000"
maxWaitMillis="30000" removeAbandonedOnBorrow="true"
removeAbandonedTimeout="300" logAbandoned="true"/>
I don't have a way to reproduce the issue, but I'm sure that the last working
release is at least tomcat-9.0.93 (possibly 9.0.94 that I'm testing now).
9.0.95 and 9.0.96 are broken
I didn't start bisecting or digging into the commits, but I think there is
something that breaks between 9.0.93 and 9.0.95
Can you tell me how I can help further to get this issue clear? Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
