Skip to main content

Quartz.NET and MEF

I have been implementing a scheduler service for several different jobs on several difference schedules, which led me into using Quartz.NET. This is a really nice framework, but since we're using MEF I ran into some issues.

Quartz.NET basically consists of the scheduler engine which runs jobs implementing the IJob interface. The interface simply consists of an Execute method. I export each job with the IJob interface using MEF.

[Export(typeof(IJob))]
public class MyJob : IJob
{
    public void Execute(JobExecutionContext context)
    {
        ...
    }
}


In my scheduler implementation the jobs are imported into an IEnumerable<IJob>.

[ImportMany(typeof(IJob))]
public IEnumerable<IJob> Jobs { get; set; }


The initialization of the scheduled tasks is pretty straight forward. A standard scheduler factory is initialized which in turn gives us a scheduler instance. Each job that was imported by MEF is then added to the scheduler, here with a simple 10 minute trigger just to make things easier.

var factory = new StdSchedulerFactory();
var scheduler = factory.GetScheduler();
foreach (var job in Jobs)
{
    var jobDetail = new JobDetail("Job name", job.GetType());
    var trigger = TriggerUtils.MakeMinutelyTrigger("Trigger name", 10, SimpleTrigger.RepeatIndefinitely);
    scheduler.ScheduleJob(jobDetail, trigger);
}


That is about everything we need to get the jobs going. The issue with MEF however is that each time a job is triggered to run the scheduler creates a new instance of the job. To prevent this behaviour we must create a custom implementation of the scheduler. The IJobFactory interface contains a NewJob method that is run each time a job is about to be run. We would like to return the same instance every time.

public class MefJobFactory : IJobFactory
{
    public IJob NewJob(TriggerFiredBundle bundle)
    {
        try
        {
            var jobs = Bootstrapper.Instance.Container.GetExports<IJob>();
            return jobs.First(job => job.GetType() == bundle.JobDetail.JobType).Value;
        }
        catch (Exception exception)
        {
            throw new SchedulerException("Problem instantiating class " + bundle.JobDetail.JobType, exception);
        }
    }
}


There is one last thing to do to actually implement this custom job factory. Nothing in the code above needs to be changed. All we have to do is to add a few lines to the app.config to instruct Quartz.NET to use our custom implementation instead of the default.

<configuration>
    <configSections>
        <section name="quartz" type="System.Configuration.NameValueSectionHandler, System, Version=1.0.5000.0,Culture=neutral, PublicKeyToken=b77a5c561934e089" />
    </configSections>
    ...
    <quartz>
        <add key="quartz.scheduler.jobFactory.type" value="MyScheduler.MefJobFactory, MyScheduler" />
    </quartz>
</configuration>


And thats it! Instead of creating a new instance of the job on each run, my custom implementation is used to get the MEF exported job.

Comments

  1. This comment has been removed by the author.

    ReplyDelete
  2. Great article on how to use Quartz.NET and MEF to schedule and execute different jobs on multiple schedules. I especially appreciate the explanation on how to solve the issue of Quartz.NET creating a new instance of the job each time it is triggered to run using a custom implementation of the IJobFactory interface.

    ReplyDelete

Post a Comment

Popular posts from this blog

Google+ finally for everyone!

There have been a lot of whining on Google from their Apps-users since the launch of  Google+  for everyone with a regular Google-account. The Apps-users have not been able to use  Google+ , until now! (actually  october 27 ) As usual I am impressed with most of the things Google accomplishes, but now when all of their services have gotten a visual and functional touchup I am getting really impressed. As someone at an early stage pointed out it is really sweet of Google to play naive and let me fill in my profile information when I create my profile (as if Google did not already know), but after a few clicks I am on the go. My albums from Picasa is automatically integrated and even the pictures I have uploaded to this blog is shown in  Google+ . But what happens next? Practically no one of my friends are on  Google+  so what do I use it for? I guess we will see. Hopefully there will be even more integration between the social networks in the future. I am anyhow very satified with

jQuery file upload with Bootstrap progress bar

Performing an asynchronous file upload from the browser is a common problem with almost as many solutions as there are developers. The following solution is the best fit for my needs, and also works well with most popular browsers. Backwards compatibility is not an issue in this case which is great, because I can use the new technologies as they are supposed to be used. Everything is put together in JSFiddle for a working example . I will continue to explain the parts below... First, the input field needs to be styled as a button. The form tag is only present for us to be able to reset the file input field later on. <form>     <span class="fileUpload btn btn-default">         <span class="glyphicon glyphicon-upload"></span> Upload file         <input type="file" id="uploadFile" />     </span> </form> .fileUpload { position: relative; overflow: hidden; } .fileUpload input { position: a