O'Reilly's Tomcat The Definitive Guide advises me to invoke the
setDaemon(true) method on any Thread object a web application creates to
keep them from hanging the JVM when Tomcat shuts down. My web service,
however, uses a thread pool that is created via
CBy wrote:
O'Reilly's Tomcat The Definitive Guide advises me to invoke the
setDaemon(true) method on any Thread object a web application creates to
keep them from hanging the JVM when Tomcat shuts down. My web service,
however, uses a thread pool that is created via
Thanks for pointing me in the right direction André. A
ServletContextListener fixed my problem.
André Warnier wrote:
CBy wrote:
O'Reilly's Tomcat The Definitive Guide advises me to invoke the
setDaemon(true) method on any Thread object a web application creates
to keep them from hanging the
CBy wrote:
Thanks for pointing me in the right direction André. A
ServletContextListener fixed my problem.
My own contribution was minimal, and due mainly to the fact that I am
eavesdropping on the real Tomcat experts conversations here and
remembering some things, even if I never used them
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carsten,
On 6/17/2009 4:33 AM, CBy wrote:
O'Reilly's Tomcat The Definitive Guide advises me to invoke the
setDaemon(true) method on any Thread object a web application creates to
keep them from hanging the JVM when Tomcat shuts down. My web
Thank you, Christopher. It appears that I now have to ways to solve my
problem. Calling shutdown() stops the threads orderly, so I think I'll
opt for the ContextListener, although I am not 100% sure.
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carsten,
On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carsten,
On 6/17/2009 2:04 PM, CBy wrote:
Thank you, Christopher. It appears that I now have to ways to solve my
problem. Calling shutdown() stops the threads orderly, so I think I'll
opt for the ContextListener, although I am not 100% sure.
I'd
