|
myeclipse开发环境
重新运行时遇到问题 无法启动 必须把tomcat下之前的部署删掉 才能重启
2013-10-12 21:47:35 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
严重: The web application [/jeecg-v3-simple] registered the JDBC driver [com.alibaba.druid.mock.MockDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
2013-10-12 21:47:35 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
严重: The web application [/jeecg-v3-simple] 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.
2013-10-12 21:47:35 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
严重: The web application [/jeecg-v3-simple] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
2013-10-12 21:47:35 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
严重: The web application [/jeecg-v3-simple] registered the JDBC driver [com.alibaba.druid.proxy.DruidDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
2013-10-12 21:47:35 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jeecg-v3-simple] appears to have started a thread named [net.sf.ehcache.CacheManager@bcbc] but has failed to stop it. This is very likely to create a memory leak.
2013-10-12 21:47:35 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jeecg-v3-simple] appears to have started a thread named [Replication Thread] but has failed to stop it. This is very likely to create a memory leak.
2013-10-12 21:47:35 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jeecg-v3-simple] appears to have started a thread named [Replication Thread] but has failed to stop it. This is very likely to create a memory leak.
2013-10-12 21:47:35 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jeecg-v3-simple] appears to have started a thread named [dictCache.data] but has failed to stop it. This is very likely to create a memory leak.
2013-10-12 21:47:35 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jeecg-v3-simple] appears to have started a thread named [eternalCache.data] but has failed to stop it. This is very likely to create a memory leak.
2013-10-12 21:47:35 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jeecg-v3-simple] 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.
2013-10-12 21:47:35 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
严重: The web application [/jeecg-v3-simple] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@14fd510]) and a value of type [org.jeecgframework.core.extend.datasource.DataSourceType] (value [dataSource_jeecg]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
2013-10-12 21:47:35 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
严重: The web application [/jeecg-v3-simple] created a ThreadLocal with key of type [net.sf.json.AbstractJSON$1] (value [net.sf.json.AbstractJSON$1@2d0e1c]) and a value of type [java.util.HashSet] (value [[]]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
2013-10-12 21:47:35 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
严重: The web application [/jeecg-v3-simple] created a ThreadLocal with key of type [net.sf.json.AbstractJSON$1] (value [net.sf.json.AbstractJSON$1@2d0e1c]) and a value of type [java.util.HashSet] (value [[]]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
|
|