-
Bug
-
Resolution: Done
-
Major
-
26.0.0.Final
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.
- is blocked by
-
WFLY-15955 Upgrade jberet-core from 1.3.11.Final to 1.3.12.Final; from 2.0.3.Final to 2.0.4.Final in ee-9 preview
- Closed
- is cloned by
-
JBERET-536 getJobInstances, getJobInstanceCount, getRunningExecutions should include jobs that have not been started
- Resolved
-
JBEAP-23114 [GSS](7.4.z) WFLY-15954 - getJobInstances, getJobInstanceCount, getRunningExecutions should include jobs that have not been started
- Closed
- relates to
-
WFLY-15921 JobOperator.getJobNames() does only return Names of Jobs that have already been executed since server start
- Closed