Tomcat 6达到最大线程数后关闭 [英] Tomcat 6 going down after reaching its maximum number of threads

查看:283
本文介绍了Tomcat 6达到最大线程数后关闭的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们的Tomcat 6.0.29在达到最大线程数后崩溃.我真的很感谢它的任何帮助,因为它是生产服务器.

Our Tomcat 6.0.29 goes down after reaching its maximum number of Threads. I would really appreciate any help with it because it is a production server.

这是catalina.log文件的一部分:

Here is part of the catalina.log file:

INFO: Maximum number of threads (600) created for connector with address null and port 80
Mar 8, 2011 11:19:37 AM org.apache.coyote.http11.Http11Protocol pause

INFO: Pausing Coyote HTTP/1.1 on http-80
Mar 8, 2011 11:19:38 AM org.apache.catalina.core.StandardService stop

INFO: Stopping service Catalina
Mar 8, 2011 11:19:38 AM org.apache.catalina.core.StandardWrapper unload

INFO: Waiting for 8 instance(s) to be deallocated

推荐答案

进行线程转储,以查看使所有线程受阻的原因.每个线程的stacktrace都比catalina.out错误更能说明您的问题.

Take a Thread Dump to see what is holding onto all your threads. The stacktrace for each thread will be an indication of your problem more then the catalina.out error was.

Windows

在控制台窗口上,按ctrl + break

Unix

在命令行中输入:kill -3 <pid>

可以在正在运行的生产实例上安全地获取这些信息.

These can be safely taken on a running production instance.

这篇关于Tomcat 6达到最大线程数后关闭的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆