tomcat意外停止,大神帮忙看下日志?报错-问答-阿里云开发者社区-阿里云

开发者社区> 问答> 正文
阿里云
为了无法计算的价值
打开APP
阿里云APP内打开

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

2020-06-12 15:26:00 673 1

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

重启服务器恢复正常

这是什么原因?

取消 提交回答
全部回答(1)
  • 爱吃鱼的程序员
    2020-06-12 15:26:19

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

    0 0
相关问答

1

回答

启动tomcat总是在启动的日志里出现这三行警报,为什么?

2016-06-02 18:36:36 2586浏览量 回答数 1

1

回答

启动tomcat总是在启动的日志里出现这三行警报

2016-03-04 09:33:26 2039浏览量 回答数 1

0

回答

启动Tomcat报错Unsupported major.minor version xxx

2021-10-28 12:08:23 294浏览量 回答数 0

1

回答

启动tomcat报错?报错

2020-06-22 19:54:15 214浏览量 回答数 1

1

回答

C3P0这是报的啥错。。。启动tomcat就报错?报错

2020-06-14 20:21:45 427浏览量 回答数 1

1

回答

启动Tomcat之后报错?报错

2020-06-14 19:05:18 154浏览量 回答数 1

1

回答

strus2启动tomcat报错,哪位大神可以指点下!?报错

2020-06-07 22:05:50 209浏览量 回答数 1

1

回答

Kylin启动时Tomcat报错,7070后台无法访问?报错

2020-06-05 15:59:29 1922浏览量 回答数 1

1

回答

winserver2008启动tomcat 报错

2017-02-25 12:18:50 1843浏览量 回答数 1

1

回答

C3P0问题,启动tomcat就报错,求助。

2016-05-31 17:01:21 1814浏览量 回答数 1
+关注
爱吃鱼的程序员
https://developer.aliyun.com/profile/5yerqm5bn5yqg?spm=a2c6h.12873639.0.0.6eae304abcjaIB
2
文章
21564
问答
问答排行榜
最热
最新
相关电子书
更多
低代码开发师(初级)实战教程
立即下载
阿里巴巴DevOps 最佳实践手册
立即下载
冬季实战营第三期:MySQL数据库进阶实战
立即下载