-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeff,
Okay, you're running into the limits of my knowledge of the APR connector's internals. On 4/13/2010 1:24 PM, Jeffrey Janner wrote: > "http-172.16.27.1-443-Acceptor-0" daemon prio=6 tid=0x6425c400 nid=0xb6c4 in > Object.wait() [0x65d7f000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0b8bafd8> (a > org.apache.tomcat.util.net.AprEndpoint$WorkerStack) > at java.lang.Object.wait(Object.java:485) > at > org.apache.tomcat.util.net.AprEndpoint.getWorkerThread(AprEndpoint.java:924) > - locked <0x0b8bafd8> (a > org.apache.tomcat.util.net.AprEndpoint$WorkerStack) > at > org.apache.tomcat.util.net.AprEndpoint$Acceptor.run(AprEndpoint.java:997) > at java.lang.Thread.run(Thread.java:619) This is the "acceptor" thread which basically accepts all the incoming requests and assigns them to worker threads: it's just a traffic cop. This thread looks like it's stuck waiting for an available worker thread (AprEndpoint.getWorkerThread) so it looks like something is definitely wrong, here. Unfortunately for you, you'll need someone like Filip who knows everything about these Connectors to comment. > <Connector address="172.16.27.1" port="443" maxHttpHeaderSize="8192" > maxThreads="150" minSpareThreads="5" maxSpareThreads="75" > enableLookups="false" acceptCount="100" It looks like a thread called "http-172.16.27.1-443-150" exists, which suggests that all maxThreads have been allocated, though they really do all look idle to me. Hmm. Yeah, wait for Filip. :) - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvEsBgACgkQ9CaO5/Lv0PCV9wCgtniW8WPI9nFm86jHxt1zPc5i kOMAnR6loJp236+HzeFER9ULkYM6TW8W =jxfF -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
