Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: override JobDetailImpl ConcurrentExecutionDisallowed property #27

Open
dariakm-i48 opened this issue Jan 28, 2021 · 0 comments

Comments

@dariakm-i48
Copy link

Versions:
Quartz.Spi.MongoDbJobStore 3.1.0

Describe:
We use Quartz.Spi.MongoDbJobStore 3.1.0 in our background job system. We have our abstraction layer above.
Jobs in our aplications have different jobs settings. Some Jobs need concurrent execution to be disallowed and some have peristend data
However, we can't use attributes [DisallowConcurrentExecutionAttribute] and [PersistJobDataAfterExecution] directly due abstraction.

Currently we override JobDetailImpl ConcurrentExecutionDisallowed property.

But due bug in MongoDbJobStore it doesn't works:

Triger didn't change state from Block to Waitting.

MongoDbJobStore method TriggerFiredInternal returns TriggerFiredBundle JobDetail with parsed settings from MongoDb (JobDetail) without override property.
Сonsequently this job can not excuted again and trigger state willn't change from Block.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant