You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2024/10/15 08:45:49 UTC
[Bug 69395] New: Empty JDBC URI when using a jdbc connection pool
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: dev@tomcat.apache.org
Reporter: agostino.sarubbo@gmail.com
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69395] Empty JDBC URI when using a jdbc connection pool
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69395
--- Comment #9 from Mark Thomas <ma...@apache.org> ---
I suggest you follow up on the users list about the JSP issue.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69395] Empty JDBC URI when using a jdbc connection pool
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69395
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|NEEDINFO |RESOLVED
--- Comment #7 from Mark Thomas <ma...@apache.org> ---
Two months without any update. Resolving as works for me.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69395] Empty JDBC URI when using a jdbc connection pool
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69395
--- Comment #4 from Agostino Sarubbo <ag...@gmail.com> ---
(In reply to Remy Maucherat from comment #3)
> (In reply to Agostino Sarubbo from comment #2)
> > 9.0.94 still works for me, the issue is in only from 9.0.95
>
> I did not mention 9.0.95 at all in my comment because the only change in it
> is a fix for a HTTP/2 regression in 9.0.94. There has to be something else
> causing your problem.
Unless I'm misunderstanding what are you saying, there are more than just a fix
for "an HTTP/2 regression in 9.0.94", at least github says this:
https://github.com/apache/tomcat/compare/9.0.94...9.0.95
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69395] Empty JDBC URI when using a jdbc connection pool
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69395
--- Comment #6 from Mark Thomas <ma...@apache.org> ---
More than a month has passed without an update. This is heading towards a
WORKSFORME resolution.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69395] Empty JDBC URI when using a jdbc connection pool
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69395
Remy Maucherat <re...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #1 from Remy Maucherat <re...@apache.org> ---
There are no relevant changes between 9.0.93 and 9.0.94, so please investigate
some more (maybe using the user list ?). "Empty JDBC URI" would be something
returned by your JDBC driver.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69395] Empty JDBC URI when using a jdbc connection pool
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69395
--- Comment #3 from Remy Maucherat <re...@apache.org> ---
(In reply to Agostino Sarubbo from comment #2)
> 9.0.94 still works for me, the issue is in only from 9.0.95
I did not mention 9.0.95 at all in my comment because the only change in it is
a fix for a HTTP/2 regression in 9.0.94. There has to be something else causing
your problem.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69395] Empty JDBC URI when using a jdbc connection pool
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69395
--- Comment #8 from Agostino Sarubbo <ag...@gmail.com> ---
Hello Mark, sorry for the late reply.
I'm not the developer of that application and in general I'm not a developer so
I can speak with a limited knowledge.
We had so far two distinct problems:
The first was related to an "Empty JDBC URI when using a jdbc connection pool"
and was resolved by adding '<load-on-startup>1</load-on-startup>' in web.xml
The other problem we are facing with >9.0.93 is that we are getting error 500
on simple jsp and tomcat does not show any stacktrace for that.
So at the begin, there was a confusion because we hit those two problems
without understand that they were two distinct problems.
I tried to activate all possible logs but tomcat still does not print anything
on error 500. Could you suggest what to modify to get a meaningful stacktrace ?
NOTE: since we are deploying a year-old untouched war we think that this error
500 comes from a tomcat change in >9.0.93
Thanks in advance
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69395] Empty JDBC URI when using a jdbc connection pool
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69395
--- Comment #2 from Agostino Sarubbo <ag...@gmail.com> ---
(In reply to Remy Maucherat from comment #1)
> There are no relevant changes between 9.0.93 and 9.0.94, so please
> investigate some more (maybe using the user list ?). "Empty JDBC URI" would
> be something returned by your JDBC driver.
Thanks for the response.
Obviously, "Empty JDBC URI" is returned by the driver. What I would pointed out
is that the same WAR returns those errors in the new version of tomcat and
works pretty well since ever.
9.0.94 still works for me, the issue is in only from 9.0.95
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69395] Empty JDBC URI when using a jdbc connection pool
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69395
--- Comment #5 from Mark Thomas <ma...@apache.org> ---
There is nothing in the 9.0.94 to 9.0.95 changes remotely related to JDBC
resources.
The full stack trace for the "Empty JDBC URI" error might be illuminating.
Bisecting the commits (there aren't that many) might be your best option at
this point.
Without evidence pointing to a Tomcat issue or a way for the committers to
reproduce the issue, this is eventually going to get resolved as WORKSFORME.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org