Uploaded image for project: 'JBeret'
  1. JBeret
  2. JBERET-536

getJobInstances, getJobInstanceCount, getRunningExecutions should include jobs that have not been started

    XMLWordPrintable

Details

    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

          Activity

            People

              cfang@redhat.com Cheng Fang
              cfang@redhat.com Cheng Fang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: