做网站出现的bug（一）

最新推荐文章于 2024-05-07 00:41:59 发布

最新推荐文章于 2024-05-07 00:41:59 发布 · 270 阅读

文章标签：

//如果你链接了数据库，更改servlet数据后，不停止tomcat就进行manager Deployments 就会不停的抛这样的严重警告
解决方法;关闭tomcat，然后在开启，然后再运行manager Deployments 下的redeploy，就ok了

2011-11-29 23:57:06 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
严重: The web application [/jiehunn] registered the JDBC 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.
2011-11-29 23:57:06 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jiehunn] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak.
2011-11-29 23:57:06 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jiehunn] appears to have started a thread named [C3P0PooledConnectionPoolManager-Helper Thread-#0] but has failed to stop it. This is very likely to create a memory leak.
2011-11-29 23:57:06 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jiehunn] appears to have started a thread named [C3P0PooledConnectionPoolManager-Helper Thread-#1] but has failed to stop it. This is very likely to create a memory leak.
2011-11-29 23:57:06 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jiehunn] appears to have started a thread named [C3P0PooledConnectionPoolManager-Helper Thread-#2] but has failed to stop it. This is very likely to create a memory leak.
2011-11-29 23:57:06 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jiehunn] appears to have started a thread named [MySQL Statement Cancellation Timer] but has failed to stop it. This is very likely to create a memory leak.
2011-11-29 23:57:06 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jiehunn] appears to have started a thread named [AWT-Windows] but has failed to stop it. This is very likely to create a memory leak.