Isn't this the difference between daemon-threads and non-daemon-threads?
The JVM waits on exit until all non-daemon-threads are finished (or was is for
daemon-threads, see the docs).
Ronald.
On Mon Mar 20 08:37:52 CET 2006 Tomcat Users List
wrote:
Hello,
I had the same question in my mi
Hello,
I had the same question in my mind some time ago. I have a web application
which creates a timer in a context listener init(), which wakes up in 30seconds
or so, and destroys the timer in context listener destroy(). It should complete
its processing before server stops, so I did some ex
Hi again,
> There's some good, in-depth discussion in the archives. It
> needs some updating, but:
> http://www.distributopia.com/servlet_stuff/background_threads.html
>
> is also reasonably informative.
Thanks a lot for mentioning this article - wow i think i could have
caused troubles on my
You can also try using the TimerTask, as follows:
In the context.xml create a bean as follows:
The TimerBean can be very simple. I typically have an init(),
destroy(), and setters for the parameters (setParam1, setParam2).
The Bean needs to create a Timer and can be used to invoke a
Tim
On Sat, 18 Mar 2006 19:32:19 +0100
"Clemens Eisserer" <[EMAIL PROTECTED]> wrote:
I've created a servlet wich creates some threads for
doing background
stuff. ... now I subscribed to a servlet-hosting service
which uses a
shared tomcat enviroment.
How does tomcat handle these threads?
Will th
