That's what I've read and from the code it's the default.

I'm hacking together a listener that rolls the entire chain from scratch rather 
than depending on the Quartz-supplied listener. I'll add some debugging logging 
and see what happens.

I might also try just creating the SchedulerFactory first, then getting a 
scheduler, then starting the scheduler, and finally adding a job.


----- Original Message ----
From: Pid <p...@pidster.com>
To: Tomcat Users List <users@tomcat.apache.org>
Sent: Mon, October 18, 2010 3:15:28 PM
Subject: Re: Tomcat memory leak error launching web app in NetBeans 6.9.1

On 18/10/2010 23:02, Mark Thomas wrote:
> On 18/10/2010 16:56, Mark Thomas wrote:
>> On 18/10/2010 12:05, Mark Eggers wrote:
>>> I saw a mention of this on the Quartz forums. People there seem to think 
>>> it's a 
>>>
>>> race condition between Quartz's scheduler shutdown and Tomcat's thread 
>>> memory 
>
>>> leak reporting.
>>
>> That is certainly possible. There was a reason I wrote the message "This
>> is very likely to create a memory leak." rather than "There is a memory
>> leak."
>>
>> Options to consider:
>> - is there a way to perform a synchronous shutdown of the scheduler?
>> - can you detect if the scheduler has not shutdown an loop (for a
>> limited time) waiting for it to finish?
> 
> Something that occurred to me just after I hit send. These threads
> really need to finish up *before* Tomcat shuts down the context. Tomcat
> does a bunch of clean-up stuff to prevent memory leaks and if
> application code is still running when the clean-up code runs the
> clean-up could easily fail.

Calling scheduler.shutdown(true); /should/ cause it to block & wait for
existing jobs to finish.

The Quartz supplied Listener does appear to do this:

http://svn.terracotta.org/fisheye/browse/Quartz/trunk/quartz/src/main/java/org/quartz/ee/servlet/QuartzInitializerListener.java?r=HEAD



p



      

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to