Re: SEVERE: All threads (200) are currently busy
Am 12.04.2015 um 02:20 schrieb HG: Every once in a while we get the following (Tomcat 6) Mar 31, 2015 7:24:32 PM org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads (200) or check the servlet status in the Catalina logs and server stops responding. The server is used very lightly and number of concurrent users not anywhere near 200 (2-3 on a busy day) The thread dump shows 199 of these: TP-Processor200 daemon prio=10 tid=0x2b513c31b000 nid=0x1c44 runnable [0x2b514a9a7000] java.lang.Thread.State: RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read1(BufferedInputStream.java:258) at java.io.BufferedInputStream.read(BufferedInputStream.java:317) - locked 0x0007873208a0 (a java.io.BufferedInputStream) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:628) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:566) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:693) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:898) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690) at java.lang.Thread.run(Thread.java:662) and one of TP-Processor4 daemon prio=10 tid=0x2b513c21a000 nid=0x7470 in Object.wait() [0x2b513552] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on 0x000784a7a208 (a org.apache.tomcat.util.threads.ThreadPool) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.threads.ThreadPool.findControlRunnable(ThreadPool.java:339) - locked 0x000784a7a208 (a org.apache.tomcat.util.threads.ThreadPool) at org.apache.tomcat.util.threads.ThreadPool.runIt(ThreadPool.java:314) at org.apache.jk.common.ChannelSocket.acceptConnections(ChannelSocket.java:676) at org.apache.jk.common.ChannelSocket$SocketAcceptor.runIt(ChannelSocket.java:879) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690) at java.lang.Thread.run(Thread.java:662) Can anybody figure out why it complaints about busy threads when they are clearly not? The first 199 are connected to a fronting web server and wait for requests on their connections. You are using a blocking connector implementation. That means each web server to Tomcat connection needs on eexclusive thread to handle it. It does not matter whether the connection already has an in-flight request on it or is completely idle. The thread is exclusively working for this single connection. Once your Tomcat has as manyconnections open in parallel as your thread pool size (or n-1), it can not accept any more connections and will log the observed message. Your can choose a mix of the following optimizations: - increase your thread pool size - configure Tomcat and for web server (Apache/mod_jk, Apache/mod_proxy_ajp, ...) to shut down idle connections more aggressively to free Tomcat threads - lower idle connection timeout (Tomcat keep alive timeout and e.g. mod_jk connection_pool_timeout) - lower the number of connections, that will be kept alive even if they are idle for a long time (mod_jk connectiopn_pool_min_size) - switch to a non blocking connector implementation like NIO. There the threads are not blocked during the time the connections are idle. Idle connections are monitored by (few, e.g. 1) poller threads and only connections with in-flight requests need a normal thread pool thread. - Make sure your web servers are not oversized in terms of their own capability on how many connections in parallel they will provide Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
SEVERE: All threads (200) are currently busy
Every once in a while we get the following (Tomcat 6) Mar 31, 2015 7:24:32 PM org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads (200) or check the servlet status in the Catalina logs and server stops responding. The server is used very lightly and number of concurrent users not anywhere near 200 (2-3 on a busy day) The thread dump shows 199 of these: TP-Processor200 daemon prio=10 tid=0x2b513c31b000 nid=0x1c44 runnable [0x2b514a9a7000] java.lang.Thread.State: RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read1(BufferedInputStream.java:258) at java.io.BufferedInputStream.read(BufferedInputStream.java:317) - locked 0x0007873208a0 (a java.io.BufferedInputStream) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:628) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:566) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:693) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:898) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690) at java.lang.Thread.run(Thread.java:662) and one of TP-Processor4 daemon prio=10 tid=0x2b513c21a000 nid=0x7470 in Object.wait() [0x2b513552] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on 0x000784a7a208 (a org.apache.tomcat.util.threads.ThreadPool) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.threads.ThreadPool.findControlRunnable(ThreadPool.java:339) - locked 0x000784a7a208 (a org.apache.tomcat.util.threads.ThreadPool) at org.apache.tomcat.util.threads.ThreadPool.runIt(ThreadPool.java:314) at org.apache.jk.common.ChannelSocket.acceptConnections(ChannelSocket.java:676) at org.apache.jk.common.ChannelSocket$SocketAcceptor.runIt(ChannelSocket.java:879) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690) at java.lang.Thread.run(Thread.java:662) Can anybody figure out why it complaints about busy threads when they are clearly not? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat 5.5.0 issue - SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Scott, On 8/24/2010 12:12 PM, Scott Hamilton wrote: You've got two connectors in that server.xml, and one of them is AJP without any real other configuration parameters. If memory serves the thread limit when not specified for a connector is 200... +1 Can we assume you're using apache as a web server connecting to tomcat? Yeah, he said that in his original original post. What are you using there - mod_proxy_ajp? Mod_jk? What do the settings for that look like? Still waiting on that information. Also, if the OP is still using 5.5.0, it's really time to upgrade to 5.5.30. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkx1aIYACgkQ9CaO5/Lv0PChmwCdFwQ6er/fHTlqh/cWJO1iFL2B eokAoKXrouSEhmYX2xBtN3PdipZiXSl1 =oDcC -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Apache 5.x issue - SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads
I have an issue where my Tomcat server is going down quite often with the following message: Aug 19, 2010 12:03:21 PM org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads (200) or check the servlet status Aug 20, 2010 4:47:20 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-9602 Aug 20, 2010 4:47:21 PM org.apache.catalina.core.StandardService stop INFO: Stopping service website Aug 20, 2010 4:47:21 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-9602 The curious thing is My MaxTrheads settings are set to 100 instead 200 as the snippet says, so I wonder from where Apache is taking this 200 I suppose this might be a hardcoded message but I need you to confirm that apache is reading my xml or not. Server.website.xml Connector port=9602 maxThreads=100 maxSpareThreads=50 minSpareThreads=10/ Please let me know whether you have information about this issue and if there's any workaround/hotfix/release where I could get this working. Thanks in advance. [reply] [-]Comment 1Mark Thomas 2010-08-24 10:16:16 ED Federico White Technical Support Specialist - Global Remote Services AVAYA | Lavalle 1877 - 7th Floor - C1051ABA | Voice US 720-444-0540| C1051ABA | Buenos Aires - Argentina - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Apache 5.x issue - SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads
From: White, Federico (Federico) [mailto:whi...@avaya.com] Subject: Apache 5.x issue - SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads First off, it's not Apache 5.x, it's Tomcat 5.x. The term Apache refers to the Apache Software Foundation, for which Tomcat is just one of many products. Tell us your exact Tomcat version, the JVM level, the platform you're running on, whether or not you're using APR, and how you start Tomcat. Server.website.xml That's not an interesting file, since Tomcat doesn't use that name. Post the conf/server.xml file that Tomcat is using, preferably with comments stripped out and privileged information obfuscated. - 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
Apache Tomcat 5.5.0 issue - SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads
Hi again, Since my first email might have not be that clear I'll re phrase it, I'm currently running a Tomcat webserver for an application that my company uses. It run's on windows server 2003, and the startup command was customized for our application and is the following C:\ProgramFiles\Avaya\IC71\tomcat\bin\tomcat5.exe//RS//AvayaICWebManag ement71 I really don't know what's the JVM level and the meaning for APR (if its really important kindly let me know how to get it and I will) We use a customized .xml file created for our product and this is the content (note we don't have the out of the box server.xml file) ?xml version=1.0 encoding=ISO-8859-1? Server port=8006 shutdown=SHUTDOWN Service name=website Connector port=9602 maxThreads=100 maxSpareThreads=50 minSpareThreads=10/ Connector port=9642 protocol=AJP/1.3 / Engine name=Catalina defaultHost=localhost Host name=localhost appBase=../comp autoDeploy=false Context docBase=C:\Program Files\Avaya\IC71/comp/website path=/website reloadable=false crossContext=true / /Host /Engine /Service /Server Thanks -Original Message- From: White, Federico (Federico) Sent: Martes, 24 de Agosto de 2010 12:09 p.m. To: 'users@tomcat.apache.org'; 'users-h...@tomcat.apache.org' Subject: Apache 5.x issue - SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads I have an issue where my Tomcat server is going down quite often with the following message: Aug 19, 2010 12:03:21 PM org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads (200) or check the servlet status Aug 20, 2010 4:47:20 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-9602 Aug 20, 2010 4:47:21 PM org.apache.catalina.core.StandardService stop INFO: Stopping service website Aug 20, 2010 4:47:21 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-9602 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Apache Tomcat 5.5.0 issue - SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads
You've got two connectors in that server.xml, and one of them is AJP without any real other configuration parameters. If memory serves the thread limit when not specified for a connector is 200... Can we assume you're using apache as a web server connecting to tomcat? What are you using there - mod_proxy_ajp? Mod_jk? What do the settings for that look like? -Original Message- From: White, Federico (Federico) [mailto:whi...@avaya.com] Sent: Tuesday, August 24, 2010 11:44 AM To: users@tomcat.apache.org Subject: Apache Tomcat 5.5.0 issue - SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads Hi again, Since my first email might have not be that clear I'll re phrase it, I'm currently running a Tomcat webserver for an application that my company uses. It run's on windows server 2003, and the startup command was customized for our application and is the following C:\ProgramFiles\Avaya\IC71\tomcat\bin\tomcat5.exe//RS//AvayaICWebManag ement71 I really don't know what's the JVM level and the meaning for APR (if its really important kindly let me know how to get it and I will) We use a customized .xml file created for our product and this is the content (note we don't have the out of the box server.xml file) ?xml version=1.0 encoding=ISO-8859-1? Server port=8006 shutdown=SHUTDOWN Service name=website Connector port=9602 maxThreads=100 maxSpareThreads=50 minSpareThreads=10/ Connector port=9642 protocol=AJP/1.3 / Engine name=Catalina defaultHost=localhost Host name=localhost appBase=../comp autoDeploy=false Context docBase=C:\Program Files\Avaya\IC71/comp/website path=/website reloadable=false crossContext=true / /Host /Engine /Service /Server Thanks -Original Message- From: White, Federico (Federico) Sent: Martes, 24 de Agosto de 2010 12:09 p.m. To: 'users@tomcat.apache.org'; 'users-h...@tomcat.apache.org' Subject: Apache 5.x issue - SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads I have an issue where my Tomcat server is going down quite often with the following message: Aug 19, 2010 12:03:21 PM org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads (200) or check the servlet status Aug 20, 2010 4:47:20 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-9602 Aug 20, 2010 4:47:21 PM org.apache.catalina.core.StandardService stop INFO: Stopping service website Aug 20, 2010 4:47:21 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-9602 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org . The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat 5.5.0 issue - SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads
On 24/08/2010 17:12, Scott Hamilton wrote: Host name=localhost appBase=../comp autoDeploy=false Context docBase=C:\Program Files\Avaya\IC71/comp/website path=/website reloadable=false crossContext=true / /Host This doesn't look right, you've got a mix of \ and / amongst other things. p 0x62590808.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
