On 4/15/2010 12:47 PM, Jeffrey Janner wrote:
Thanks Konstantin -
That's a possibility.  Is it feasible that all 150 worker threads would enter 
await before the Acceptor thread got some CPU time again?  I guess so.  I 
suppose setting the priority of the Acceptor thread higher than the workers 
would minimize the chances of this happening.
I dropped them back to a 1.5 JVM and made it through the night last night, 
though that might have just been lower load on the system as well.  It only 
opened about 135 worker threads.
Hopefully, 5.5.30 will be along faster than 5.5.29.  I'm still waiting on 
whomever to put the Windows installer version out there for that.

If you already have an installation, you don't need a windows installation package to install the updates. Just unzip the package on top of your old installation, and everything will be updated (assuming it's the same base version, such as upgrading from 5.5.20 to 5.5.30).

-----Original Message-----
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Sent: Thursday, April 15, 2010 9:20 AM
To: Tomcat Users List
Subject: Re: Hung threads

2010/4/13 Christopher Schultz<ch...@christopherschultz.net>:
Hash: SHA1


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-" 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 
       at java.lang.Object.wait(Object.java:485)
       - locked<0x0b8bafd8>  (a 
       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.

If it is stuck there, it will not accept any more incoming requests.

It might be that you bumped into BZ 48843

A patch for it is already available, proposed, and has enough votes,
so it will be applied shortly. That will be 5.5.30, though.

Unfortunately for you, you'll need someone like Filip who knows
everything about these Connectors to comment.

     <Connector address="" port="443" maxHttpHeaderSize="8192"
                maxThreads="150" minSpareThreads="5" maxSpareThreads="75"
                enableLookups="false" acceptCount="100"

It looks like a thread called "http-" exists, which
suggests that all maxThreads have been allocated, though they really do
all look idle to me. Hmm.

Yeah, wait for Filip. :)

Best regards,
Konstantin Kolinko

To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

*******************************  NOTICE  *********************************
This message is intended for the use of the individual or entity to which
it is addressed and may contain information that is privileged,
confidential, and exempt from disclosure under applicable law.  If the
reader of this message is not the intended recipient or the employee or
agent responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution, or copying
of this communication is strictly prohibited.  If you have received this
communication in error, please notify us immediately by reply or by
telephone (call us collect at 512-343-9100) and immediately delete this
message and all its attachments.

To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to