ThreadPool logFull issue
Hi Friends, I have found an exception( org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (150) are currently busy, waiting. Increase maxThreads (150) ) in my Tomcat server in last weekend. Ideall no body was using the application that time and this error came up. Could you please any of you tell me what caused the exception and usually what are the possible reasons for this issue.? My JDK version: 1.5.0_16 Tomcat Version: 5.0.28 OS: unix Thansk,
RE: ThreadPool logFull issue
From: Phani Raj Kumar [mailto:bphanirajku...@gmail.com] Subject: ThreadPool logFull issue org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (150) are currently busy, waiting. Take a thread dump and find out what the threads are doing. (The logFull notation is a bit of a concern.) Tomcat Version: 5.0.28 Not supported; please move to a Tomcat level that is. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: ThreadPool logFull issue
Caldarale, Charles R wrote: From: Phani Raj Kumar [mailto:bphanirajku...@gmail.com] Subject: ThreadPool logFull issue org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (150) are currently busy, waiting. Take a thread dump and find out what the threads are doing. (The logFull notation is a bit of a concern.) I'm fairly sure it is harmless. logFull is the name of a boolean used to track if the logFull (ie log that that thread pool is full) message has been previously reported. Mark Tomcat Version: 5.0.28 Not supported; please move to a Tomcat level that is. +1 Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Realtime notification of ThreadPool logFull
Nelson, Tracy wrote:
Why not just grab the source
I looked at the source (org.apache.tomcat.util.threads.ThreadPool) and it IS
logging to the commons logger - see below.
private static void logFull(Log loghelper, int currentThreadCount,
int maxThreads) {
if( logfull ) {
log.error(sm.getString(threadpool.busy,
new Integer(currentThreadCount),
new Integer(maxThreads)));
logfull=false;
} else if( log.isDebugEnabled() ) {
log.debug(All threads are busy + currentThreadCount + +
maxThreads );
}
}
But this is NOT the log I am getting in catalina.out. Instead, I am getting,
Nov 17, 2006 12:08:25 PM org.apache.tomcat.util.threads.ThreadPool logFull
SEVERE: All threads (10) are currently busy, waiting. Increase maxThreads.
What gives? I am getting other normal info, etc ... level messages but not
this one. Using v5.5.17.
Jeff
--
View this message in context:
http://www.nabble.com/Realtime-notification-of-ThreadPool-logFull-tf2654425.html#a7419824
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Realtime notification of ThreadPool logFull
your diagnostic appears out of sync with your source
where did you acquire the source?
M-
This e-mail communication and any attachments may contain confidential and
privileged information for the use of the
designated recipients named above. If you are not the intended recipient, you
are hereby notified that you have received
this communication in error and that any review, disclosure, dissemination,
distribution or copying of it or its
contents
- Original Message -
From: jwboring [EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent: Saturday, November 18, 2006 9:27 AM
Subject: RE: Realtime notification of ThreadPool logFull
Nelson, Tracy wrote:
Why not just grab the source
I looked at the source (org.apache.tomcat.util.threads.ThreadPool) and it IS
logging to the commons logger - see below.
private static void logFull(Log loghelper, int currentThreadCount,
int maxThreads) {
if( logfull ) {
log.error(sm.getString(threadpool.busy,
new Integer(currentThreadCount),
new Integer(maxThreads)));
logfull=false;
} else if( log.isDebugEnabled() ) {
log.debug(All threads are busy + currentThreadCount + +
maxThreads );
}
}
But this is NOT the log I am getting in catalina.out. Instead, I am getting,
Nov 17, 2006 12:08:25 PM org.apache.tomcat.util.threads.ThreadPool logFull
SEVERE: All threads (10) are currently busy, waiting. Increase maxThreads.
What gives? I am getting other normal info, etc ... level messages but not
this one. Using v5.5.17.
Jeff
--
View this message in context:
http://www.nabble.com/Realtime-notification-of-ThreadPool-logFull-tf2654425.html#a7419824
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Realtime notification of ThreadPool logFull
Martin Gainty wrote: your diagnostic appears out of sync with your source. where did you acquire the source? The app is deployed under the the binary distribution gotten from the web site (http://tomcat.apache.org/download-55.cgi). We do not compile from the source, at least not yet. I only got the source to check the log code. Source came from the archives (http://archive.apache.org/dist/tomcat/tomcat-5/v5.5.17/). Can anyone explain the log message I am getting that does not appear to be to commons log? I'll install v5.5.20 Monday from binary and see if I get the same strange log. Jeff -- View this message in context: http://www.nabble.com/Realtime-notification-of-ThreadPool-logFull-tf2654425.html#a7424775 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Realtime notification of ThreadPool logFull
Hi Jeff,
jwboring schrieb:
private static void logFull(Log loghelper, int currentThreadCount,
int maxThreads) {
if( logfull ) {
log.error(sm.getString(threadpool.busy,
new Integer(currentThreadCount),
new Integer(maxThreads)));
Most likely this is the one you are interested in!
logfull=false;
} else if( log.isDebugEnabled() ) {
log.debug(All threads are busy + currentThreadCount + +
maxThreads );
}
}
But this is NOT the log I am getting in catalina.out. Instead, I am getting,
Nov 17, 2006 12:08:25 PM org.apache.tomcat.util.threads.ThreadPool logFull
SEVERE: All threads (10) are currently busy, waiting. Increase maxThreads.
What gives? I am getting other normal info, etc ... level messages but not
this one. Using v5.5.17.
Jeff
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Realtime notification of ThreadPool logFull
I need to be notified when ever a Tomcat v5.5 server is over the threadpool limit. I am already monitoring log4j log messages but the logFull message appears to me to be a System.out log, by-passing log4j (catalina.out text shown below). Nov 17, 2006 12:08:25 PM org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (10) are currently busy, waiting. Increase maxThreads If my above assumption is correct, how can I monitor ThreadPool logFull messages without reading the catalina.out file and parsing? Also, I'm aware of the ThreadPool mbean and already use JMX to query this mbean to display it's properties. However, I don't believe this mbean supports JMX notifications. Of course, I could spawn a thread every X minutes but that seems dumb. Can I do this with a LifeCycle Listener? Is there a way to get log4j messages e.g., log.error(logFull SEVERE: All threads ...) from the ThreadPool object? Jeff -- View this message in context: http://www.nabble.com/Realtime-notification-of-ThreadPool-logFull-tf2654425.html#a7405640 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Realtime notification of ThreadPool logFull
| From: jwboring [mailto:[EMAIL PROTECTED] | Sent: Friday, 17 November, 2006 10:39 | | I need to be notified when ever a Tomcat v5.5 server is over the | threadpool | limit. I am already monitoring log4j log messages but the logFull message | appears to me to be a System.out log, by-passing log4j (catalina.out text | shown below). Why not just grab the source and modify it to Take Appropriate Action (log to a standard logging stream, launch an external command, whatever) when that condition occurs? It can't be that hard to find where the error message is coming from and add a little code. The information contained in this message is confidential proprietary property of FACTS/Nelnet Business Solutions. Any reproduction, forwarding, or copying without the express permission of FACTS/Nelnet Business Solutions is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this e-mail. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ThreadPool logFull
I was stress-testing for our web application we always meet this TreadPool logFull. I have been doing some research and found our I can change the maximum number of thread in the server.xml. However, surfing the net i found some said that is not the real solution. I am not sure why and if anyone knows the real solution let me know. SK - Original Message - From: Len Popp [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Tuesday, July 25, 2006 6:26 PM Subject: Re: Possible to send 503 status over JK? The recent messages on this topic have confused me, so I've spent part of my evening running some tests. = First, with Tomcat standalone: Tomcat's default error pages can be overridden by an error-page declaration in the webapp's web.xml. If there is no error-page declared, Tomcat uses its default error page; it does *not* fall back to a global error page declared in the ROOT webapp. When a webapp is stopped, its error pages are not executed (obviously), so Tomcat's default error pages are used. Therefore it is not possible to override the 503 page when the webapp is stopped. Tomcat always uses its default page. In any case, the correct HTTP status code is returned to the browser. = With Tomcat behind Apache and mod_jk: As long as Tomcat is running, the situation is the same as above. JK and Apache pass Tomcat's error pages and status codes back unchanged. ErrorDocument declarations do not override Tomcat's error pages. When Tomcat is down (not just one webapp stopped, but Tomcat not running at all), you obviously don't get a Tomcat error page. Apache generates the 503 error and uses its own error page. This page can be overridden by ErrorDocument. Again, the correct HTTP status codes are returned to the browser. So, you can use a custom ErrorDocument to return a Site Down message if Tomcat is down completely, but not if a webapp inside Tomcat is stopped. These tests were done with Tomcat 5.5.17, Apache 2.0.55, JK 1.2.15. -- Len On 7/25/06, Hassan Schroeder [EMAIL PROTECTED] wrote: On 7/25/06, Rick G [EMAIL PROTECTED] wrote: The 500 is caught correctly, but I always end up seeing the tomcat generated error page for a 503. I guess this could be a mod_jk or apache issue if you are saying that tomcat is sending the right status code. Questions: what version of tomcat you running? that quick test was on 5.5.17 standalone just to confirm the correct http header was being sent. -- Hassan Schroeder [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ThreadPool logFull, Tomcat not responding anymore
Konrath Thomas [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi .. We have a problem on our product server with our web application (which is too complicated to go into the details of here). Every day at least once our web application is mysteriously hanging. The application don't seem to crash or emit error messages, it just stop responding. In the catalina.out file I found the following error message: Nov 23, 2005 2:15:39 PM org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (75) are currently busy, waiting. Increase maxThreads (75) or check the servlet status = complete error message below The exception should be fixed in the latest SVN code. I've no idea when 4.1.32 is going to be release however. I have search in the internet for this problem. It seems that increasing the number of max threads is not the solution. The problem will be still there, just with the new max thread number. I have found several postings, describes this problem on a Red Hat Server (like http://mail-archives.apache.org/mod_mbox/jakarta-tomcat-user/200408.mbox /[EMAIL PROTECTED]). On Linux machines, this is generally true. The work-around is to set a connectionTimeout=6 (you'll probably have to tune the value for your system) on the Connector element in server.xml. This tells Tomcat to release any thread that hasn't done anything in the last minute. Our configuration is: Jakarta Tomcat 4.1.31 j2sdk 1.4.2_06 Suse Linux Enterprise Server 8 Please note that this server is not under our control. It is controlled by the IT department of our customer. We have no root privileges on the server!!! So we are not able to create a stack thumb of the threads up to now. But we are working on it ... The APR and (experimental) NIO AJP/1.3 Connectors are designed to deal with this problem. However, to get them, you either have to build TC 4.1 from SVN or upgrade to TC 5.5. Can anyone help me or give me a hint to solve this problem??? kind regards Tom Nov 23, 2005 2:15:39 PM org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (75) are currently busy, waiting. Increase maxThreads (75) or check the servlet status Nov 23, 2005 4:05:27 PM org.apache.commons.modeler.Registry registerComponent SEVERE: Error registering Catalina:type=RequestProcessor,worker=jk-8017,name=JkRequest10631 javax.management.InstanceAlreadyExistsException: Catalina:type=RequestProcessor,worker=jk-8017,name=JkRequest10631 at mx4j.server.MBeanServerImpl.register(MBeanServerImpl.java:1123) at mx4j.server.MBeanServerImpl.registerImpl(MBeanServerImpl.java:1054) at mx4j.server.MBeanServerImpl.registerMBeanImpl(MBeanServerImpl.java:1002) at mx4j.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:978) at org.apache.commons.modeler.Registry.registerComponent(Registry.java:871) at org.apache.jk.common.ChannelSocket.registerRequest(ChannelSocket.java:43 6) at org.apache.jk.common.HandlerRequest.decodeRequest(HandlerRequest.java:44 3) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:352) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java: 675) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:683) at java.lang.Thread.run(Thread.java:534) Nov 23, 2005 4:05:27 PM org.apache.jk.common.ChannelSocket registerRequest WARNING: Error registering request - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
