Comments on: Scheduling tasks with Quartz http://karlagius.com/2009/12/02/scheduling-tasks-with-quartz/ It's not rocket science Sat, 05 Jun 2010 12:11:00 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Mrinal http://karlagius.com/2009/12/02/scheduling-tasks-with-quartz/comment-page-1/#comment-1023 Mrinal Wed, 30 Dec 2009 21:16:51 +0000 http://karlagius.com/?p=356#comment-1023 It is a clean re-deploy, meaning the entire ear file gets re-deployed. The J2EE container does not re-start though, only my application. Yes, the scheduler is started automatically. It is a clean re-deploy, meaning the entire ear file gets re-deployed. The J2EE container does not re-start though, only my application. Yes, the scheduler is started automatically.

]]> By: Antonio Santiago http://karlagius.com/2009/12/02/scheduling-tasks-with-quartz/comment-page-1/#comment-1021 Antonio Santiago Wed, 30 Dec 2009 10:48:38 +0000 http://karlagius.com/?p=356#comment-1021 Mrinal, do you make a "clean" redeploy with the WAR file or it is a "ugly" (sorry by the expression) redeploy uploading only some java files with the changes? The first one must run fine. Mrinal,
do you make a “clean” redeploy with the WAR file or it is a “ugly” (sorry by the expression) redeploy uploading only some java files with the changes?
The first one must run fine.

]]> By: Karl http://karlagius.com/2009/12/02/scheduling-tasks-with-quartz/comment-page-1/#comment-1020 Karl Wed, 30 Dec 2009 09:55:26 +0000 http://karlagius.com/?p=356#comment-1020 Hi. Do you have any log output? Could be getting stuck somewhere. Also, is the scheduler started automatically with your application? If I understood what you're saying correctly, it works just after you define the task, so it's possible that it's only being started at that point. What happens if you schedule <em>another</em> task? Do both the old task and the new one run then? Hi. Do you have any log output? Could be getting stuck somewhere.

Also, is the scheduler started automatically with your application? If I understood what you’re saying correctly, it works just after you define the task, so it’s possible that it’s only being started at that point.

What happens if you schedule another task? Do both the old task and the new one run then?

]]> By: Mrinal http://karlagius.com/2009/12/02/scheduling-tasks-with-quartz/comment-page-1/#comment-1016 Mrinal Tue, 29 Dec 2009 22:40:59 +0000 http://karlagius.com/?p=356#comment-1016 I have a webapp, which embeds the quartz scheduler. I am seeing that when I schedule a recurring job with cron expression, say hourly, it works fine. But when I update the webapp, with some unrelated new code, and re-deploy the webapp, the hourly job does not run anymore, even though I can still see it in WAIT state on the db. Any idea? I have a webapp, which embeds the quartz scheduler. I am seeing that when I schedule a recurring job with cron expression, say hourly, it works fine. But when I update the webapp, with some unrelated new code, and re-deploy the webapp, the hourly job does not run anymore, even though I can still see it in WAIT state on the db. Any idea?

]]> By: Karl http://karlagius.com/2009/12/02/scheduling-tasks-with-quartz/comment-page-1/#comment-979 Karl Wed, 09 Dec 2009 21:48:35 +0000 http://karlagius.com/?p=356#comment-979 Thank you for your comment, Antonio. Good point about stateful jobs. In my case it is only a personal preference. Maybe I'm a little paranoid too, but self contained tasks have a kind of appeal for me. Thank you for your comment, Antonio. Good point about stateful jobs. In my case it is only a personal preference. Maybe I’m a little paranoid too, but self contained tasks have a kind of appeal for me.

]]> By: Antonio Santiago http://karlagius.com/2009/12/02/scheduling-tasks-with-quartz/comment-page-1/#comment-978 Antonio Santiago Wed, 09 Dec 2009 21:22:25 +0000 http://karlagius.com/?p=356#comment-978 I found important in some projects the fact to distinguish about stateless and statefull jobs. Supposing the jobs are fired by a cron trigger it can be helpful to not start a job until the previous is finished. In that situations the stateful jobs are nice. Nice post. I think quartz needs more documentation and this post is a step more on that. I found important in some projects the fact to distinguish about stateless and statefull jobs.
Supposing the jobs are fired by a cron trigger it can be helpful to not start a job until the previous is finished. In that situations the stateful jobs are nice.

Nice post. I think quartz needs more documentation and this post is a step more on that.

]]> By: Karl http://karlagius.com/2009/12/02/scheduling-tasks-with-quartz/comment-page-1/#comment-977 Karl Wed, 09 Dec 2009 10:37:45 +0000 http://karlagius.com/?p=356#comment-977 I'm afraid I haven't touched Seam yet :$ How do you find it in comparison to Spring as a web application framework? I’m afraid I haven’t touched Seam yet :$ How do you find it in comparison to Spring as a web application framework?

]]> By: Yonathan http://karlagius.com/2009/12/02/scheduling-tasks-with-quartz/comment-page-1/#comment-976 Yonathan Wed, 09 Dec 2009 08:37:43 +0000 http://karlagius.com/?p=356#comment-976 There is also good support for quartz in Seam framework. Very easy to configure. There is also good support for quartz in Seam framework. Very easy to configure.

]]> By: Karl http://karlagius.com/2009/12/02/scheduling-tasks-with-quartz/comment-page-1/#comment-975 Karl Wed, 09 Dec 2009 08:13:08 +0000 http://karlagius.com/?p=356#comment-975 Thanks for the tip, Leo :) Thanks for the tip, Leo :)

]]> By: leo http://karlagius.com/2009/12/02/scheduling-tasks-with-quartz/comment-page-1/#comment-974 leo Wed, 09 Dec 2009 07:50:48 +0000 http://karlagius.com/?p=356#comment-974 Hey, If your running quartz in an appserver, make sure you make it use the threadpool provided by the appserver. One downside of quartz is still that it even then it creates one unmanaged thread by itselves which might lead to issues in production as we have seen on our websphere servers... otherwise great framework especially in combination with a spring application. Greetz Leo Hey,

If your running quartz in an appserver, make sure you make it use the threadpool provided by the appserver. One downside of quartz is still that it even then it creates one unmanaged thread by itselves which might lead to issues in production as we have seen on our websphere servers… otherwise great framework especially in combination with a spring application.

Greetz Leo

]]>