上午9点23分,网站访问不了,这是tomcat的日志:
Aug 3, 2015 12:06:18 AM org.apache.coyote.http11.AbstractHttp11Processor process INFO: Error parsing HTTP request header Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level. Aug 3, 2015 1:43:32 AM org.apache.coyote.http11.AbstractHttp11Processor process INFO: Error parsing HTTP request header Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level. Aug 3, 2015 3:24:12 AM org.apache.coyote.http11.AbstractHttp11Processor process INFO: Error parsing HTTP request header Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level. Aug 3, 2015 5:15:39 AM org.apache.coyote.http11.AbstractHttp11Processor process INFO: Error parsing HTTP request header Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level. Aug 3, 2015 9:00:03 AM org.apache.coyote.http11.AbstractHttp11Processor process INFO: Error parsing HTTP request header Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level. Aug 3, 2015 9:33:15 AM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler ["http-bio-80"] Aug 3, 2015 9:33:16 AM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler ["ajp-bio-8009"] Aug 3, 2015 9:33:18 AM org.apache.catalina.core.StandardService stopInternal INFO: Stopping service Catalina Aug 3, 2015 9:33:18 AM org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 198 instance(s) to be deallocated for Servlet [default] Aug 3, 2015 9:33:19 AM org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 198 instance(s) to be deallocated for Servlet [default] Aug 3, 2015 9:33:20 AM org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 198 instance(s) to be deallocated for Servlet [default] Aug 3, 2015 9:33:20 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: The web application [] 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 3, 2015 9:33:20 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation. Aug 3, 2015 9:33:20 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation. Aug 3, 2015 9:33:20 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation. Aug 3, 2015 9:33:20 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation. Aug 3, 2015 9:33:20 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation. Aug 3, 2015 9:33:20 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
:java.net.connectexception: connection timed out
重启服务器恢复正常
这是什么原因?
如果你用tomcat连接池了,那就是你的jdbc连接超时了,导致你的应用不能运行,给你一段我的连接池属性吧:driverClassName="com.mysql.jdbc.Driver"auth="Container"type="javax.sql.DataSource"testOnBorrow="true"validationQuery="select1"validationInterval="30000" 连接超时!
版权声明:本文内容由阿里云实名注册用户自发贡献,版权归原作者所有,阿里云开发者社区不拥有其著作权,亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容,填写侵权投诉表单进行举报,一经查实,本社区将立刻删除涉嫌侵权内容。