NO errors logged anywhere.  That's the really frustrating part of it.
That and that I cannot reproduce it using in-house clients against the
server during the day.
I haven't bothered to crank up to debug either, since it's a production
system.
I want to lean to there being an issue with 1.1.18 native, since that's
the only recent change that was still in effect.  I backed that down to
the previous version, but the end users haven't used the system yet to
check if that is the issue.
I do have a 1.1.16 version on a system that does not show the problem.


-----Original Message-----
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] 
Sent: Friday, April 16, 2010 4:10 PM
To: Tomcat Users List
Subject: Re: Hung threads

2010/4/16 Jeffrey Janner <jeffrey.jan...@polydyne.com>
> Well, it's definitely deadlocking once it hits the maxThreads limit.

The worker is returned to the workers pool by an
AprEndpoint.recycleWorkerThread(..) call. If that call is skipped, the
workers will leak. That is theoretically. I do not remember any
reports on such an issue.

Do you have any error messages in your logs,  or in the catalina.out
file (aka the file that catches your stderr stream)?

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

Reply via email to