-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
When stopping a batch job execution, jberet currently keeps the batch status STOPPING in memory only, and only persist the batch status after the job execution has been stopped.
Strictly speaking, the batch status STOPPING should be persisted to job repository immediatly to truly reflect its execution status. To support that, JobRepository interface and its impl in WildFly JobRepositoryService will need to be updated with additional operation.
- is blocked by
-
WFLY-14637 Upgrade jberet-core from 1.3.7.Final to 1.3.8.Final
-
- Closed
-
- is cloned by
-
-
- Closed
-
- is related to
-
JBERET-508 Stop batch job execution from a different node
-
- Resolved
-
