Org. Apache. Catalina. loader. webappclassloader clearreferencesjdbc
Severe: the Web application [/RDMS] registered the jbdc driver [COM. mySQL. JDBC. driver] but failed to unregister it when the web application was stopped. to prevent a memory leak, the JDBC driver has been forcibly unregistered.
After I searched the internet, many people said this problem. I think the cause may be a variety of reasons, not a fixed one. I will briefly talk about the situation I found and solve this problem with myself.
There is a foreignerArticleHttp://confluence.atlassian.com/pages/viewpage.action? Pageid = 218275753
It has the following reasons:
Causes
There is? Memory leak detection feature introduced in Tomcat 6.0.25 that attempts to log objects that have failed to be garbage collected even though they been marked for removal. as the Tomcat and JVM is being shutdown, these messages are not applicable in this situation.
That is to say, after Tomcat 6.025, memory leakage detection has been introduced. For images that cannot be processed by garbage collection, logs will be generated.
The method proposed by foreigners is either to use the old version of Tomcat or to put
<! -- Prevent memory leaks due to use of particle Java/javax APIs -->
<Listener classname = "org. Apache. Catalina. Core. jrememoryleakpreventionlistener"/>;
This listener is disabled. I tried to shut down the listener and won't report the above information. But I don't know if there will be any other problems when running Tomcat like this.