You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Caldarale, Charles R" <Ch...@unisys.com> on 2009/05/19 15:09:32 UTC
RE: Running out of tomcat threads - why many threads in
RUNNABLEstageeven with no activity
> From: Christopher Schultz [mailto:chris@christopherschultz.net]
> Subject: Re: Running out of tomcat threads - why many threads in
> RUNNABLEstageeven with no activity
>
> Or, maybe Java's thread states don't differentiate between
> actually runnable and runnable but blocked (as opposed to
> WAITING which means waiting on a synchronization monitor).
Correct; there is no BLOCKED state from the point of view of a Java thread. When in native code, such as reading from a socket or any other JNI method, the thread is still considered RUNNABLE, since the VM has no control over when it might be executing.
- 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.