tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 52025] 7.0.21 and newer break the JDK 6 Service provider mechanism for loading JDBC Drivers
Date Mon, 17 Oct 2011 14:03:30 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=52025

--- Comment #9 from Konstantin Kolinko <knst.kolinko@gmail.com> 2011-10-17 14:03:30
UTC ---
(In reply to comment #7)
> I am closing this as INVALID as the Service Provider mechanism for
> DriverManager is - as I suspected - broken for servlet container environments.

The scan for service providers happens only once when DriverManager
initializes. See DriverManager.getDrivers() /
DriverManager.loadInitialDrivers(). (JDK 6u26)

1. My understanding regarding DriverManager.getDrivers() call in
JreMemoryLeakPreventionListener is that Service Provider mechanism should work
if the class is visible to the JreMemoryLeakPreventionListener.

That is, it should work if the driver jar is in $CATALINA_BASE\lib

It might be nice to mention it in the docs, because it might be useful for
users, but I have not tested whether it actually works.


2. I agree with Mark that for webapps it is broken at JRE level and cannot be
fixed, thus INVALID. Even if you disable the listener, at most one webapp per
JVM would be able to make use of it.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- 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


Mime
View raw message