Comments on: Reliable job scheduling with NServiceBus and Quartz.NET http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/ Strong opinions, weakly held Wed, 22 May 2013 13:39:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Distributed Weekly 168 — Scott Banwart's Blog http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4827 Distributed Weekly 168 — Scott Banwart's Blog Fri, 17 Aug 2012 10:24:45 +0000 http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4827 [...] Reliable job scheduling with NServiceBus and Quartz.NET [...] [...] Reliable job scheduling with NServiceBus and Quartz.NET [...]

]]> By: Anonymous http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4822 Anonymous Tue, 14 Aug 2012 14:33:00 +0000 http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4822 That's basically what the built-in scheduler in NServiceBus does. It works really well for interval-based ones that use a time span to determine cadence of firing. But not so hot for specific schedule-based ones, where it's sensitive to run on explicit dates/times. I've gotten the push back before on not taking on a 3rd-party tool for scheduling, but I guess I just prefer not to build infrastructure components myself. That’s basically what the built-in scheduler in NServiceBus does. It works really well for interval-based ones that use a time span to determine cadence of firing.

But not so hot for specific schedule-based ones, where it’s sensitive to run on explicit dates/times. I’ve gotten the push back before on not taking on a 3rd-party tool for scheduling, but I guess I just prefer not to build infrastructure components myself.

]]> By: Anonymous http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4821 Anonymous Tue, 14 Aug 2012 14:30:00 +0000 http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4821 There's two things here - one is, did the Quartz job not fire to send the original message. In that case, we audit jobs from Quartz to make sure they get fired w/o errors. In the handler side, because we're using NServiceBus, if the handler fails, the message retries. If it fails after that, the message drops into an error queue, which we also monitor. Does that make sense? There’s two things here – one is, did the Quartz job not fire to send the original message. In that case, we audit jobs from Quartz to make sure they get fired w/o errors.

In the handler side, because we’re using NServiceBus, if the handler fails, the message retries. If it fails after that, the message drops into an error queue, which we also monitor. Does that make sense?

]]> By: Anonymous http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4820 Anonymous Tue, 14 Aug 2012 14:27:00 +0000 http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4820 Ha wow. Maybe we can throw in calling a sproc and have it call out to COM too? Ha wow. Maybe we can throw in calling a sproc and have it call out to COM too?

]]> By: The Morning Brew - Chris Alcock » The Morning Brew #1167 http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4819 The Morning Brew - Chris Alcock » The Morning Brew #1167 Tue, 14 Aug 2012 08:31:55 +0000 http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4819 [...] Reliable job scheduling with NServiceBus and Quartz.NET - Jimmy Bogard takes a look at task scheduling, and looks at a solution which combines Quartz.NET for the scheduling part and NServiceBus for the actual execution of the tasks. [...] [...] Reliable job scheduling with NServiceBus and Quartz.NET – Jimmy Bogard takes a look at task scheduling, and looks at a solution which combines Quartz.NET for the scheduling part and NServiceBus for the actual execution of the tasks. [...]

]]> By: RichB http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4817 RichB Tue, 14 Aug 2012 06:35:00 +0000 http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4817 > It forced us to create console apps for everything Not true. You could have used a cscript script to call into a ServicedComponent via COM+. Then you get the lovely benefits of strong naming. Really. > It forced us to create console apps for everything

Not true. You could have used a cscript script to call into a ServicedComponent via COM+. Then you get the lovely benefits of strong naming. Really.

]]> By: Mike Mozhaev http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4818 Mike Mozhaev Tue, 14 Aug 2012 06:35:00 +0000 http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4818 How is "job failed to start" handled? How is “job failed to start” handled?

]]> By: Maksim http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4816 Maksim Mon, 13 Aug 2012 22:46:00 +0000 http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4816 Have anyone considered using NServiceBus "timeout manager" alone for that? In that case, for every job we would have a handler that decides whether job should be executed or not (in case of server restart/failover), defers message for next execution and executes job itself. I believe it is also a little bit of code, but instead we could remove unnecessary dependencies. Have anyone considered using NServiceBus “timeout
manager” alone for that? In that case, for every job we would have a handler that decides whether
job should be executed or not (in case of server restart/failover), defers message for next execution and executes job itself.

I believe it is also a little bit of code, but
instead we could remove unnecessary dependencies.

]]> By: Joseph Daigle http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4815 Joseph Daigle Mon, 13 Aug 2012 21:02:00 +0000 http://lostechies.com/jimmybogard/2012/08/13/reliable-job-scheduling-with-nservicebus-and-quartz-net/#comment-4815 We've used this exact setup in production for some time now (over a year). It works perfectly and is really easy to troubleshoot and manage. We’ve used this exact setup in production for some time now (over a year). It works perfectly and is really easy to troubleshoot and manage.

]]>