-
Bug
-
Resolution: Done
-
Major
-
None
The fix to WFLY-15921 introduced some change of behavior wrt suspend and restart:
So when there's an unfinished execution in the repository DB at startup and no new executions were started yet since the crash:
- before the patch: getJobNames() returns empty, so no getRunningExecutions(jobName) calls
- after the patch: getJobNames() returns a set of all defined job names, resulting in getRunningExecutions(jobName) calls
This issue is to address this change of behavior so the batch subssytem will behave the same as before fixing WFLY-15921 wrt server suspend and restart.
- is cloned by
-
JBEAP-23323 [GSS](7.4.z) WFLY-16112 - Batch JobOperatorService should look for only active job names to stop during suspend
- Closed
- relates to
-
WFLY-15921 JobOperator.getJobNames() does only return Names of Jobs that have already been executed since server start
- Closed