The only one that I'm aware of is that if you don't setDaemon(true), then
shutting down tomcat will hang until the thread completes.
George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
-Original Message-
From: Thom Hehl [mailto:[EMAIL PROTECTED]
Sent:
Most of the time people will tell you don't do it, but don't get any
more specific than that. Generally-speaking, spawning a thread to
process a request is somewhat of a bad idea because the container is not
responsible for managing the thread and therefore you run some extra
risks. But, if
-Original Message-
From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 14, 2006 1:20 PM
To: Tomcat Users List
Subject: Re: Spawning a thread
risks. But, if you have something like a background process
that isn't
tied to a request, with the caveat
Subject: Re: Spawning a thread
risks. But, if you have something like a background process
that isn't
tied to a request, with the caveat the other poster made about daemon
A good way of starting threads not tied to a request is to have a context
listener class start the threads
Subject: Re: Spawning a thread
risks. But, if you have something like a background process that
isn't tied to a request, with the caveat the other poster made about
daemon
A good way of starting threads not tied to a request is to have a context
listener class start the threads and handle
From: Thom Hehl [mailto:[EMAIL PROTECTED]
Subject: Re: Spawning a thread
Can you point me to some documentation about context listener
threads?
Context listeners are classes, not threads. The servlet spec is the
definitive doc, but there's not a great deal of how-to in there:
http
