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.

Sign up for GitHub

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

Jump to bottom

Timer job never unlocked after an exception #3913

Open
silentjesse126 opened this issue Jun 21, 2024 · 0 comments
Open

Timer job never unlocked after an exception #3913

silentjesse126 opened this issue Jun 21, 2024 · 0 comments

Comments

@silentjesse126
Copy link

silentjesse126 commented Jun 21, 2024 •
edited
Loading

Describe the bug
please refer to #2354

Expected behavior
I think there's still a possibility to have a lock, now UnlockTimerJobsCmd is run in the catch code block, but there is no chance to execute this code block when the app process is closed by exception.

Additional context
Need a thread "ResetExpiredTimerJobsRunnable" run on an independent Thread just like ResetExpiredJobsRunnable, the lock happens in any exception will be unlocked.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@silentjesse126