Using SQL Server with MSMQ¶
This extension will be deprecated soon
Hangfire.SqlServer 1.7.X versions have long-polling feature implemented when using the recommended settings with the latest schema version. Additional technology like MSMQ complicates the application infrastructure, additional storage like MSMQ brings consistency issues on data loss, and MSMQ itself is a complicated technology, especially with DTC transactions. Therefore, the number of disadvantages outweigh all the advantages of using this extension.
Hangfire.SqlServer.MSMQ extension changes the way Hangfire handles job queues. Default implementation uses regular SQL Server tables to organize queues, and this extensions uses transactional MSMQ queues to process jobs. Please note that starting from 1.7.0 it’s possible to use TimeSpan.Zero as a polling delay in Hangfire.SqlServer, so think twice before using MSMQ.
Installation¶
MSMQ support for SQL Server job storage implementation, like other Hangfire extensions, is a NuGet package. So, you can install it using NuGet Package Manager Console window:
PM> Install-Package Hangfire.SqlServer.Msmq
Configuration¶
To use MSMQ queues, you should do the following steps:
Create them manually on each host. Don’t forget to grant appropriate permissions. Please note that queue storage is limited to 1048576 KB by default (approximately 2 millions enqueued jobs), you can increase it through the MSMQ properties window.
Register all MSMQ queues in current
SqlServerStorageinstance.
If you are using only default queue, call the UseMsmqQueues method just after UseSqlServerStorage method call and pass the path pattern as an argument.
GlobalConfiguration.Configuration
.UseSqlServerStorage("<connection string or its name>")
.UseMsmqQueues(@"FormatName:Direct=OS:localhost\hangfire-{0}");
To use multiple queues, you should pass them explicitly:
GlobalConfiguration.Configuration
.UseSqlServerStorage("<connection string or its name>")
.UseMsmqQueues(@"FormatName:Direct=OS:localhost\hangfire-{0}", "critical", "default");
Limitations¶
Only transactional MSMQ queues supported for reliability reasons inside ASP.NET.
You can not use both SQL Server Job Queue and MSMQ Job Queue implementations in the same server (see below). This limitation relates to Hangfire Server only. You can still enqueue jobs to whatever queues and watch them both in Hangfire Dashboard.
Transition to MSMQ queues¶
If you have a fresh installation, just use the UseMsmqQueues method. Otherwise, your system may contain unprocessed jobs in SQL Server. Since one Hangfire Server instance can not process job from different queues, you should deploy multiple instances of Hangfire Server, one listens only MSMQ queues, another – only SQL Server queues. When the latter finish its work (you can see this in Dashboard – your SQL Server queues will be removed), you can remove it safely.
If you are using default queue only, do this:
/* This server will process only SQL Server table queues, i.e. old jobs */
var oldStorage = new SqlServerStorage("<connection string or its name>");
var oldOptions = new BackgroundJobServerOptions();
app.UseHangfireServer(oldOptions, oldStorage);
/* This server will process only MSMQ queues, i.e. new jobs */
GlobalConfiguration.Configuration
.UseSqlServerStorage("<connection string or its name>")
.UseMsmqQueues(@"FormatName:Direct=OS:localhost\hangfire-{0}");
app.UseHangfireServer();
If you use multiple queues, do this:
/* This server will process only SQL Server table queues, i.e. old jobs */
var oldStorage = new SqlServerStorage("<connection string>");
var oldOptions = new BackgroundJobServerOptions
{
Queues = new [] { "critical", "default" }, // Include this line only if you have multiple queues
};
app.UseHangfireServer(oldOptions, oldStorage);
/* This server will process only MSMQ queues, i.e. new jobs */
GlobalConfiguration.Configuration
.UseSqlServerStorage("<connection string or its name>")
.UseMsmqQueues(@"FormatName:Direct=OS:localhost\hangfire-{0}", "critical", "default");
app.UseHangfireServer();