Vjeran Marcinko wrote:
----- Original Message ----- From: "Berin Loritsch"
<[EMAIL PROTECTED]> To: "Avalon framework users"
<[EMAIL PROTECTED]> Sent: Thursday, June 12, 2003 3:39 PM
Subject: Re: [Event] Zombie threads - HELP - dunno Linux
So what you are saying is that the threads do not naturally clean
themselves up like they do in other operating systems? How about
when the parent process is terminated?
I am wanting to figure this out, because I want to see if there is
an issue with the thread pooling code that we have.
I'm sort of thinking the same thing because of the following ... My
app is actually a chat server based on fortress and I could see today
it's threads (and the only ones I know of are from Event package)
going zombie even if this server hasn't done anything today - not
even one client connection came...It was idle, waiting for client
connections for whole day, and even in this inactive state threads
were going zombie. So I asked myself what is active in it if it's not
processing client connections, and the only answer I could find is -
some internal scheduler maybe who checks periodically for incoming
commands to be processed by worker threads (thread pool) ?
We are using Doug Lea's concurrency code which includes a Thread Pool
(more specifically a PooledExecutor). I know it will close threads
that are not in use, but it is unclear if it "joins" them or not.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
