Hangfire Mysql integration No support specifying queues directly #10102

4 Answer(s)

• 

  0

  AI-Bot created 5 hours ago

  Support Team ABP Agent

  1. Solution

  • Root cause

    • Hangfire.MySqlStorage (v2.0.3) does not support passing the queue name to RecurringJob.AddOrUpdate via options for a specific job. ABP’s HangfireBackgroundWorkerManager uses Hangfire’s RecurringJob.AddOrUpdate with a queue parameter for some internal background workers (e.g., token/audit cleanup), which triggers “Current storage doesn't support specifying queues directly for a specific job. Please use the QueueAttribute instead.” MySQL storage provider throws NotSupportedException in this case.
    • With Redis storage, specifying queues per job is supported; therefore it works.

  • What you can do

    1. Preferred: Switch to an implementation that supports per-job queues

       • Use a Hangfire storage provider that supports per-job queue selection (e.g., Redis, SQL Server). Your existing Redis setup already works.

    2. Or, keep MySQL but disable ABP’s Hangfire background workers and use a different background worker implementation in ABP

       • Replace ABP’s Hangfire-based background workers with Quartz for the “background workers” part, while still using Hangfire for BackgroundJobs if you need it. ABP allows mixing implementations:
         • Install and depend on AbpBackgroundWorkersQuartzModule in your Domain layer to run ABP’s internal workers (cleanup, etc.) with Quartz (which doesn’t use Hangfire queues).
         • Keep Hangfire only for BackgroundJobs (IBackgroundJobManager) if you still want Hangfire for enqueueing fire-and-forget jobs. If using MySQL storage for Hangfire, avoid per-job queue customization from your own jobs (or mark job classes with [Queue] attribute only if your storage supports it).

       Example module setup:

  [DependsOn(
           typeof(AbpBackgroundWorkersQuartzModule), // run ABP workers via Quartz
           typeof(AbpBackgroundJobsModule) // keep generic jobs; add Hangfire only if you need it
           // typeof(AbpBackgroundJobsHangfireModule) // include only if you will use Hangfire for IBackgroundJobManager
       )]
       public class MyProjectDomainModule : AbpModule
       {
           public override void PreConfigureServices(ServiceConfigurationContext context)
           {
               // Configure Quartz persistence (e.g., MySQL/PostgreSQL/SQL Server)
               PreConfigure<AbpQuartzOptions>(options =>
               {
                   options.Configurator = cfg =>
                   {
                       cfg.UsePersistentStore(store =>
                       {
                           store.UseProperties = true;
                           store.UseJsonSerializer();
                           store.UseMySql("Your MySQL connection string"); // or other provider
                       });
                   };
               });
           }
       }
  

   - In your web host, remove AddHangfireServer if you don’t need Hangfire workers at all, or keep it only for background jobs that don’t specify per-job queue options in a way MySQL storage rejects.
   - ABP’s internal workers (Identity session cleanup, token cleanup, audit log cleanup, etc.) will run under Quartz and won’t call Hangfire. That sidesteps the Hangfire/MySQL queue limitation.
  

  3. If you must stay with Hangfire + MySQL for everything
     • This combination is currently incompatible with ABP’s internal workers that specify queues per job. There’s no knob in ABP to stop it from passing the queue to RecurringJob.AddOrUpdate for those workers.
     • Unless Hangfire.MySqlStorage adds support for per-job queue selection via recurring jobs, the only options are:
       • Contribute a PR to Hangfire.MySqlStorage to support queues passed during RecurringJob.AddOrUpdate, or
       • Fork ABP’s HangfireBackgroundWorkerManager to remove the queue parameter (not recommended; you’ll diverge from ABP).

  • Minimal change recipe (keeps MySQL, removes the crash)
    • Keep your Hangfire.MySqlStorage registration if you still want Hangfire to store BackgroundJobs.
    • Add Quartz for background workers and disable ABP’s Hangfire workers by not depending on AbpBackgroundWorkersHangfireModule anywhere. Ensure your Solution depends on AbpBackgroundWorkersQuartzModule.
    • Result: ABP internal workers run on Quartz; Hangfire remains usable for IBackgroundJobManager. No crash.

  2. Sources

  • HangfireBackgroundWorkerManager (ABP source – shows how ABP registers recurring jobs and passes queue):
    • https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.BackgroundWorkers.Hangfire/Volo/Abp/BackgroundWorkers/Hangfire/HangfireBackgroundWorkerManager.cs

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Save Cancel
• 

  0

  maliming created 12 minutes ago

  Support Team Fullstack Developer

  hi

  What is your abp package version?

  Save Cancel
• 

  0

  maliming created 9 minutes ago

  Support Team Fullstack Developer

  https://github.com/arnoldasgudas/Hangfire.MySqlStorage doesn't support the latest Hangfire >=1.8.0

  see https://github.com/HangfireIO/Hangfire/issues/2319#issuecomment-1933619870

  Save Cancel
• 

  0

  maliming created 7 minutes ago

  Support Team Fullstack Developer

  You can also try to override the HangfireBackgroundWorkerManager

  https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.BackgroundWorkers.Hangfire/Volo/Abp/BackgroundWorkers/Hangfire/HangfireBackgroundWorkerManager.cs#L18

  Just remove the Queue from RecurringJob.AddOrUpdate

  Thanks.

  Save Cancel