Add ApplicationName
property to isolate jobs/workers.
#22169
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #22081
No breaking changes are caused by default.
A breaking change label was added because the database migration needs to be added.
If you have multiple applications using one storage as background jobs and workers(
Default, Hangfire, RabbitMQ, and Quartz
), You should set the provider options to use the application name to isolate.Default Background Job:
Set
ApplicationName
ofAbpBackgroundJobWorkerOptions
to your application name.Hangfire:
Set
DefaultQueuePrefix
ofAbpHangfireOptions
to your application name.RabbitMQ:
Set
DefaultQueueNamePrefix
andDefaultDelayedQueueNamePrefix
ofAbpRabbitMqBackgroundJobOptions
to your application name.Quartz:
Set
quartz.scheduler.instanceName
to your application name.You can use this
app
to test: https://github.com/abpframework/abp/tree/BackgroundJob-ApplicationName-Test/modules/background-jobs/appIf there is no problem, I will update the document later.