主题 : 启动没有报错,运行没有反应,也没有报错。 |
级别: 秀才
|
1# 发表于:2018-08-16 18:00:00 IP:125.205.*.*
|
||||
---|---|---|---|---|---|
级别: 总版主
|
5# 发表于:2018-08-17 09:02:36 IP:117.92.*.*
|
||
---|---|---|---|
级别: 秀才
|
7# 发表于:2018-08-17 09:07:13 IP:122.232.*.*
补充,启动快完成的时候的log,我感觉问题就出现在这些log中:
Aug 16, 2018 8:46:49 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesJdbc SEVERE: The web application [/jeecmsv9f] 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. Aug 16, 2018 8:46:49 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesJdbc SEVERE: The web application [/jeecmsv9f] 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. Aug 16, 2018 8:46:49 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [/jeecmsv9f] appears to have started a thread named [Timer-2] but has failed to stop it. This is very likely to create a memory leak. Aug 16, 2018 8:46:49 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [/jeecmsv9f] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak. Aug 16, 2018 8:46:49 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [/jeecmsv9f] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak. Aug 16, 2018 8:46:49 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [/jeecmsv9f] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak. Aug 16, 2018 8:46:49 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [/jeecmsv9f] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak. Aug 16, 2018 8:46:49 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deployment of web application archive /usr/liangliang/tomcat/apache-tomcat-7.0.78/webapps/jeecmsv9f.war has finished in 17,522 ms Aug 16, 2018 8:46:53 PM org.apache.catalina.loader.WebappClassLoaderBase findResourceInternal INFO: Illegal access: this web application instance has been stopped already. Could not load . The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. Aug 16, 2018 9:11:10 PM org.apache.catalina.startup.HostConfig undeploy INFO: Undeploying context [/jeecmsv9f] Aug 16, 2018 9:15:30 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive /usr/liangliang/tomcat/apache-tomcat-7.0.78/webapps/jeecmsv9f.war Aug 16, 2018 9:15:35 PM org.apache.catalina.startup.TldConfig execute INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. Aug 16, 2018 9:15:46 PM org.apache.catalina.core.StandardContext startInternal SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file Aug 16, 2018 9:15:46 PM org.apache.catalina.core.StandardContext startInternal SEVERE: Context [/jeecmsv9f] startup failed due to previous errors Aug 16, 2018 9:15:46 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesJdbc SEVERE: The web application [/jeecmsv9f] 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. Aug 16, 2018 9:15:46 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesJdbc SEVERE: The web application [/jeecmsv9f] 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. Aug 16, 2018 9:15:46 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [/jeecmsv9f] appears to have started a thread named [Timer-3] but has failed to stop it. This is very likely to create a memory leak. Aug 16, 2018 9:15:46 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [/jeecmsv9f] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak. Aug 16, 2018 9:15:46 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [/jeecmsv9f] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak. Aug 16, 2018 9:15:46 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [/jeecmsv9f] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak. Aug 16, 2018 9:15:46 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [/jeecmsv9f] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak. Aug 16, 2018 9:15:46 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deployment of web application archive /usr/liangliang/tomcat/apache-tomcat-7.0.78/webapps/jeecmsv9f.war has finished in 15,563 ms Aug 16, 2018 9:15:50 PM org.apache.catalina.loader.WebappClassLoaderBase findResourceInternal INFO: Illegal access: this web application instance has been stopped already. Could not load . The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. |
||
---|---|---|---|