> 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 h
o: 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 the other poster made about
daemon
A good way of starting threads not tied to a request is to have a context
listener cl
Thom Hehl wrote:
Can you point me to some documentation about context listener threads? I
have no idea what you're talking about.
Just a simple overview of application Events and Listeners, but it
should give you the idea:
http://e-docs.bea.com/wls/docs70/webapp/app_events.html#175768
Cheer
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 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 t
> -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
>
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
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:
