Default Background Job is not working as expected

[ArcherTrister]

Is there an existing issue for this?

• I have searched the existing issues

Description

I have multiple services, each using the Default Background Job. All services share a single database for Background Jobs. After configuring according to the documentation, it d not work as expected: the ApplicationName field in the AbpBackgroundJobs table is always empty, and all Background Jobs are executed in the main application, causes errors when executing jobs for other services.

Reproduction Steps

Add the same configuration to each service according to the description in the documentation.

Expected behavior

The value of the ApplicationName field in the AbpBackgroundJobs table is not null, and each service can execute its respective Background Job.

Actual behavior

Always execute Background Job in a service.

Regression?

No response

Known Workarounds

Configuration should be performed in the ConfigureServices method.

Version

9.3.7

User Interface

Common (Default)

Database Provider

EF Core (Default)

Tiered or separate authentication server

None (Default)

Operation System

macOS

Other information

No response

[maliming]

Hi,

Thanks for the report. You are right, the documentation sample is wrong. PreConfigure<AbpBackgroundJobWorkerOptions> only stores the action into a PreConfigureActionList<T> and requires someone to call ExecutePreConfiguredActions<AbpBackgroundJobWorkerOptions>() to actually apply it, but nothing in the background jobs module does that, so ApplicationName stays null.

Your workaround is the correct fix, please use ConfigureServices + Configure<AbpBackgroundJobWorkerOptions> instead:

public override void ConfigureServices(ServiceConfigurationContext context)
{
    Configure<AbpBackgroundJobWorkerOptions>(options =>
    {
        options.ApplicationName = context.Services.GetApplicationName()!;
    });
}

I've updated the docs in #25292.

Thanks