Hi,
Hmm, then is there a recommended way for managing child threads that
are
kicked off by a servlet? My servlet reads an XML file to determine what
classes to create and run - but if the Servlet itself goes away and
then
is re-init()ed it will attempt to start those classes again. Does every
Great ideas Yoav. Thank you for your comments/input.
--JW
Shapira, Yoav wrote:
Hi,
Hmm, then is there a recommended way for managing child threads that
are
kicked off by a servlet? My servlet reads an XML file to determine what
classes to create and run - but if the Servlet itself goes
If upgrading Tomcat is possible, a context listener would be a better
design.
On Mon, 2004-10-18 at 15:51, Jonathan Wilson wrote:
I have a load-on-startup1/load-on-startup Servlet on TC3.3.1(under
RH7.3) which checks an XML file which contains a list of Runnable
classes to kick off at
I'm working on getting the next release out on TC5. I don't think that
would fix my threading issue, however.
JW
Ben Souther wrote:
If upgrading Tomcat is possible, a context listener would be a better
design.
On Mon, 2004-10-18 at 15:51, Jonathan Wilson wrote:
I have a
Hi,
servlet). These are daemon threads, and have the setDaemon(true) set
for
the thread before I kickoff the runnable class. The problem I'm
experiencing is that when the context needs to be reloaded these child
threads are not killed, but continue to run.
Why would they be killed? The JVM
Hi,
Shapira, Yoav wrote:
Hi,
servlet). These are daemon threads, and have the setDaemon(true) set
for
the thread before I kickoff the runnable class. The problem I'm
experiencing is that when the context needs to be reloaded these child
threads are not killed, but continue to run.
