-
Enhancement
-
Resolution: Done
-
Major
-
None
-
False
-
False
-
-
-
-
-
-
+
-
Steps to reproduce:
- Deploy the attached modified EAP batch-processing quickstart ( [^batch-processing-quickstart.zip] )
- On the started server open [_http://localhost:8080/batch-processing/_]
- Push the 'Log JobNames' button and see the log message in the server.log
- Push the 'Generate a new file and start import job' button and afterwards the 'Log JobNames' button again. Afterwards, see the server.log again
Is this expected behavior? Shouldn't the 1st usage of the 'Log JobNames' button already show all JobNames?
- causes
-
JBEAP-23114 [GSS](7.4.z) WFLY-15954 - getJobInstances, getJobInstanceCount, getRunningExecutions should include jobs that have not been started
- Closed
- clones
-
WFLY-15921 JobOperator.getJobNames() does only return Names of Jobs that have already been executed since server start
- Closed
- is related to
-
JBEAP-23323 [GSS](7.4.z) WFLY-16112 - Batch JobOperatorService should look for only active job names to stop during suspend
- Closed