开发者社区> 问答> 正文

tomcat意外停止,大神帮忙看下日志?报错

上午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.



结束tomcat,报错:

:java.net.connectexception: connection timed out

重启服务器恢复正常

这是什么原因?

展开
收起
爱吃鱼的程序员 2020-06-12 15:26:00 1140 0
1 条回答
写回答
取消 提交回答
  • https://developer.aliyun.com/profile/5yerqm5bn5yqg?spm=a2c6h.12873639.0.0.6eae304abcjaIB

    如果你用tomcat连接池了,那就是你的jdbc连接超时了,导致你的应用不能运行,给你一段我的连接池属性吧:driverClassName="com.mysql.jdbc.Driver"auth="Container"type="javax.sql.DataSource"testOnBorrow="true"validationQuery="select1"validationInterval="30000" 连接超时!

    2020-06-12 15:26:19
    赞同 展开评论 打赏
问答排行榜
最热
最新

相关电子书

更多
大规模日志数据平台架构面临的问题与挑战 立即下载
PostgresChina2018_赖思超_PostgreSQL10_hash索引的WAL日志修改版final 立即下载
Kubernetes下日志实时采集、存储与计算实践 立即下载