flowable / flowable/flowable-engine

Timer job never unlocked after an exception

Aperta
#3,913 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Java
Stelle
9.5k
Fork
2.9k
Merge medio
7h 8m
PR unite (30g)
2

Descrizione

**Describe the bug**
please refer to https://github.com/flowable/flowable-engine/issues/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.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.