Scheduler stops after a period of time with Quartz 1.61

[seema-7]

After a varied period of time the scheduler stops triggering. I can see that this has been a problem with older versions. Has there been any solution to this.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=483721#483721


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[seema-7]

What type of jobs are you using? The job type/nature of the job code is what could cause problems?
or
How's your network? I know someone who had that problem because port 8080 was not available for their tomcat server.
or
what's up with your connection pooling/datasource?

or
did you pas all of this already?

M : (

Message was edited by:
        michael.clayton@...
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=483845#483845


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[seema-7]

I am just using a SimpleTrigger with JobDetail. I am not using the web version.
The scheduler is started with the following properties.

#============================================================================
# Configure Main Scheduler Properties  
#============================================================================

org.quartz.scheduler.instanceName = Sched1
org.quartz.scheduler.rmi.export = true
org.quartz.scheduler.rmi.registryHost = localhost
org.quartz.scheduler.rmi.registryPort = 1099
org.quartz.scheduler.rmi.createRegistry = true

#============================================================================
# Configure ThreadPool  
#============================================================================

org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 10
org.quartz.threadPool.threadPriority = 5

#============================================================================
# Configure JobStore  
#============================================================================

org.quartz.jobStore.misfireThreshold = 60000

org.quartz.jobStore.class = org.quartz.simpl.RAMJobStore
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=483895#483895


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[seema-7]

What code is starting this scheduler?
M:)
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=485418#485418


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[seema-7]

I have a class that I use to send wrap around the scheduler.
When I start I have the following code to start the scheduler.

try {
            System.setProperty("org.quartz.properties","server.properties");
            SchedulerFactory sf = new StdSchedulerFactory();
            sched = sf.getScheduler();
            sched.addSchedulerListener(this);
            try {
                sched.addTriggerListener(this);
            } catch (SchedulerException ex) {
                System.out.println("" + ex);
            } catch (Exception e) {
                System.out.println("" + e);
            }
            sched.start();
            log.info("Scheduler started");
            setConnected();
        } catch (SchedulerException ex1)
        {
            log.error("connectToRemoteServer:"+ex1);
            setDisconnected();
        }


Cheers Kelvin
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=485855#485855


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[seema-7]

Ok, I kinda see what is going on.
I had the same problem using RMI with quartz, I can tell it's RMI because you are using server.properties.

Unfortunately, I did not get the RMI way to stay alive either.
I have had great success using tomcat with QuartzInitializer Servlet!
M : )
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=485882#485882


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[seema-7]

Yes, and I have tried running it as standalone with RMI, and it still only runs for a couple of hours. Maybe I should try it as a servlet.

Kelvin
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=486102#486102


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[seema-7]

sorry, meant to say WITHOUT RMI
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=486111#486111


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[seema-7]

Remember,

if your JVM dies, your scheduler will too: especially if it's standalone!

M : )
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=486124#486124


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[seema-7]

Hi Michael. Thanks for the time you are putting into this.

The JVM is still running. To me it looks like the Threads in the pool just stop. I don't have a profiler running to test this. I have also check the Jobs that are being execute to see if something is getting blocked, but nothing at this stage.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=486149#486149


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[seema-7]

if u configure it correctly with quartz init servlet, you won't have to explicitly log anything, it will happen automatically(or schedually, get it scheduler?)
M : )
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=486295#486295


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[seema-7]

Sorry for the late reply, I have been out travelling. I have given up using it as a standalone and set it up as a servlet. The initial test show that this seems to work.

Kelvin
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=509463#509463


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[seema-7]

Told ya!

M : ))
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=509468#509468


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[seema-7]

Hi,

I have a similar problem: whenever I use a stateful job with 1.6.1 RC1, the scheduler stops firing jobs after 5 or 10 minutes (sometimes it never stops). Using only stateless jobs [b]or[/b] 1.5.2 —and changing nothing else in code or configuration— is enough to solve the problem.

I’m doing nothing fancy (they all say that, right?), have only a few jobs, use the RAM job store, the default quartz.properties, one cron trigger per job. Maybe something: I’m running Quartz as part of an Eclipse application, with the jar repackaged as a plug-in.

Other than that, Quartz works great, I’m happy with using 1.5.2.

Cheers.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=514687#514687


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[seema-7]

Why are you not using 1.6.0?
Why 1.5.2 or 1.6.1 or bust?
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=515286#515286


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[seema-7]

Please try it with version 1.6.0.  If you see the problem there, then post something to the Quartz Developers forum since it appears to be a regression.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=396606&messageID=515304#515304


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...