Well, I believe I've identified and run the thread dumps as suggested. I am
using default Quartz properties without any customisations of my own in a
dedicated properties file. The job is set to print out a message every
minute and appears to be fine.
This is an extract from the first dump where Tomcat 6.0.26 was started
within NetBeans 6.9.1. It shows ten or so Quartz threads as I would expect:
"DefaultQuartzScheduler_Worker-1" prio=6 tid=0x03d0d400 nid=0x3008 in
Object.wait() [0x0441f000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x28e00778> (a
org.quartz.simpl.SimpleThreadPool$WorkerThread)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:543
)
- locked <0x28e00778> (a
org.quartz.simpl.SimpleThreadPool$WorkerThread)
Locked ownable synchronizers:
- None
And then when I terminate the Quartz application, but leave Tomcat running,
the second dump appears to be show no trace of these messages at all. So
does this indicate that Quartz has shut down but only after my application
has stopped within Tomcat, i.e. that Tomcat monitors my application's demise
and reports the threads as extant because Quartz has not yet ended?
Full dumps are available if required.
-----Original Message-----
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: 19 Oct 2010 16 57
To: Tomcat Users List
Subject: RE: Tomcat memory leak error launching web app in NetBeans 6.9.1
> From: app...@dsl.pipex.com [mailto:app...@dsl.pipex.com]
> Subject: Re: Tomcat memory leak error launching web app in NetBeans 6.9.1
> Where there are fewer messages but it still seems as if
> Tomcat is detecting Quartz threads after Quartz is shut down.
Which means Quartz isn't really shutting down. As suggested before, take
some thread dumps and find out what the threads are doing that prevents them
from going away. That may uncover some other problem in your webapp.
> So my simple question becomes: do these messages matter
> if Tomcat is restarted or if the host server (which starts
> Tomcat as a Windows service) is rebooted?
No. However, I would be concerned that this aberration is just a symptom of
something more serious that might be wrong. For example, are the threads
stuck on some lock that they shouldn't be? Are other resources tied up that
might cause instability over the long term? Sweeping the problem under the
rug by rebooting would leave me a bit uneasy.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
