-
Bug
-
Resolution: Done
-
Major
-
7.4.1.GA, 7.12.0.GA, 7.13.0.GA
-
- RHPAM with EJB timer with DB persistence
-
False
-
None
-
False
-
Release Notes
-
-
-
-
-
-
CR1
-
?
-
https://github.com/kiegroup/jbpm/pull/2154, https://github.com/kiegroup/jbpm/pull/2167, https://github.com/kiegroup/jbpm/pull/2170, https://github.com/kiegroup/jbpm/pull/2169, https://github.com/kiegroup/jbpm/pull/2197, https://github.com/kiegroup/jbpm/pull/2196, https://github.com/kiegroup/jbpm/pull/2274, https://github.com/kiegroup/jbpm/pull/2276, https://github.com/kiegroup/jbpm/pull/2275
-
-
---
-
---
-
2022 Week 23-25 (from Jun 6), 2022 Week 26-28 (from Jun 27), 2022 Week 29-31 (from Jul 18), 2022 Week 32-34 (from Aug 8)
Aborting a process instance with an active timer does not cancel this timer.
The timer then fires at the defined trigger date, which is silently dismissed by the system, so this is not a functional problem. However, it populates the EJB timer subsystem with "orphaned" timers, in particular if the timers are long-running, and the number of aborted process instances is high.
- is cloned by
-
JBPM-10087 Timer not deleted at process instance abort
- Closed
- mentioned on