I've tracked the problem 'til Doug Lea's PooledExecutor. See the shutdownAfter family methods. They seems to never get rid of the threads as they are not signaled in any way.
The shutdownNow on the other hand relies on the Thread.interrupt call to force an InterruptedException. The fact is that the thread must be on a blocking operation to InterruptedException be throwed. So some of the threads are disposed after calling shutdownNow. I'll contact Doug Lea directly to handle those issues. Cheers, hammett -----Mensagem original----- De: Berin Loritsch [mailto:[EMAIL PROTECTED] Enviada em: ter�a-feira, 13 de julho de 2004 15:57 Para: Hamilton Verissimo de Oliveira (Engenharia - SPO) Cc: [EMAIL PROTECTED]; Excalibur Developers List Assunto: Re: Event package Hamilton Verissimo de Oliveira (Engenharia - SPO) wrote: > Hey, dude! > > I've been digging into your code and checked out that its not exposed as an > avalon component :-O > But something like the dipose lyfecycle is necessary to kill the thread > group. I'm thinking about using the finalize as a 'temporary' work around. > WDYT? Sounds good. We need to make that happen in the Fortress code as well though. I really don't think it was to begin with--which is why at times I am stuck with threads keeping the JVM open with the last release of Fortress. -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rich Cook --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
