Posted By: Anonymous
I am getting this message when I run my web application. It runs fine but I get this message during shutdown.
SEVERE: A web application registered the JBDC driver [oracle.jdbc.driver.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Any help appreciated.
Since version 6.0.24, Tomcat ships with a memory leak detection feature, which in turn can lead to this kind of warning messages when there’s a JDBC 4.0 compatible driver in the webapp’s
/WEB-INF/lib which auto-registers itself during webapp’s startup using the
ServiceLoader API, but which did not auto-deregister itself during webapp’s shutdown. This message is purely informal, Tomcat has already taken the memory leak prevention action accordingly.
What can you do?
Ignore those warnings. Tomcat is doing its job right. The actual bug is in someone else’s code (the JDBC driver in question), not in yours. Be happy that Tomcat did its job properly and wait until the JDBC driver vendor get it fixed so that you can upgrade the driver. On the other hand, you aren’t supposed to drop a JDBC driver in webapp’s
/WEB-INF/lib, but only in server’s
/lib. If you still keep it in webapp’s
/WEB-INF/lib, then you should manually register and deregister it using a
Downgrade to Tomcat 6.0.23 or older so that you will not be bothered with those warnings. But it will silently keep leaking memory. Not sure if that’s good to know after all. Those kind of memory leaks are one of the major causes behind
OutOfMemoryErrorissues during Tomcat hotdeployments.
Move the JDBC driver to Tomcat’s
/libfolder and have a connection pooled datasource to manage the driver. Note that Tomcat’s builtin DBCP does not deregister drivers properly on close. See also bug DBCP-322 which is closed as WONTFIX. You would rather like to replace DBCP by another connection pool which is doing its job better then DBCP. For example HikariCP or perhaps Tomcat JDBC Pool.