Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
False
-
+
Description
There are 2 EE TCK batch test failures that might have been caused by the fix to WFLY-15921.
com/ibm/jbatch/tck/tests/jslxml/JobOperatorTests.java#testJobOpgetJobInstanceCount_from_ejb
com/ibm/jbatch/tck/tests/jslxml/JobOperatorTests.java#testJobOpgetJobInstanceCount_from_web
So we should apply the same idea to getJobInstances, getJobInstanceCount, getRunningExecutions methods as well, to include jobs that are in the deployment but have not been started.
Attachments
Issue Links
- clones
-
WFLY-15954 getJobInstances, getJobInstanceCount, getRunningExecutions should include jobs that have not been started
- Closed
- is caused by
-
JBEAP-23107 [GSS](7.4.z) WFLY-15921 - JobOperator.getJobNames() does only return Names of Jobs that have already been executed since server start
- Verified