Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 95664 invoked by uid 500); 16 Oct 2001 07:55:21 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 95631 invoked from network); 16 Oct 2001 07:55:20 -0000 X-Authentication-Warning: jeeves.stud.ntnu.no: endrs owned process doing -bs Date: Tue, 16 Oct 2001 09:55:28 +0200 (MEST) From: =?iso-8859-1?Q?Endre_St=F8lsvik?= X-X-Sender: To: Subject: Re: StandardManager In-Reply-To: Message-ID: X-My-Opinion: War and bombs are bad. Peace and flowers are good. ;-D MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Sat, 13 Oct 2001, Prashant Rao wrote: | But as soon as the stress thest was stopped the house keeping thread | (StandardManager) started to drop all the sessions. This sounds like the StandardManager thread could be running on a lower priority. This because lower priority threads in Java apparently are guaranteed to starve if there are other higher pri (normal, then) which wants to do work.. Could this be it? I have no clue as of the pri of the manager (or anything else of the internals of Tomcat, to be honest), but it sure sounds like a thread starvation problem. Anyways it sounds like something that definately shouldn't happen. One thing, though: why/how did the serialization mechanism kick in? I thought that would be handled by the manager too? Endre. -- Mvh, Endre