[Bug 55368] Default Tomcat install is no longer auto-registering JDBC type 4 drivers

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=55368

Nick Williams <ni...@nicholaswilliams.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|                            |All

--- Comment #1 from Nick Williams <ni...@nicholaswilliams.net> ---
I'll wait for someone more knowledgeable to chime in, but if I remember the
discussion correctly this is actually the intended behavior.

DriverManager is really just a big memory leak waiting to happen. If you load a
JDBC Driver from the wrong ClassLoader (for example, if you put a JDBC driver
in /WEB-INF/lib, which you really shouldn't do anyway), when it registers with
the DriverManager the Class and Driver instance leak into the System
ClassLoader. The Driver can then be accessed from any code in the JVM,
including other web applications. This is a design flaw in the DriverManager
(at least, many people feel that way) that will probably never be fixed.

IIRC, the fix for bug 51640 intentionally resulted in stopping DriverManager
from automatically discovering and loading Drivers because that was the best
way to fix the problem. But I could be mistaken.

-- 
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