-
Bug
-
Resolution: Done
-
Major
-
7.3.5.GA
-
None
-
False
-
False
-
-
-
-
-
-
+
-
Undefined
-
The following problem was reported by user:
I have 2 JBoss instances sharing the same JobRepository. So on both instances one can see the executions for both instances. When I start an Execution on - let's say - node 1 and restart that same execution on node 2, then node 2 will start a new Execution starting from the last commited checkpoint while the first Execution keeps running on node 1. So now I have two Executions processing the same Items.
When I check the status of the Execution running on node 1 from node 2, I can see that it is in STARTED state. But the JobOperators ignores that and restarts it anyway.
- clones
-
JBERET-508 Stop batch job execution from a different node
- Resolved
-
JBERET-509 Restart batch job execution from a different node
- Resolved
-
JBEAP-21442 [GSS](7.4.z) JBERET-508 - Restart batch job execution from a different node
- Closed
- is incorporated by
-
JBEAP-21443 (7.3.z) Upgrade jberet from 1.3.7.Final-redhat-00001 to 1.3.8.Final-redhat-00001
- Closed
- is related to
-
JBEAP-21805 (7.3.z) WFLY-14619 - Stop batch job execution from a different node
- Closed