Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-15921

JobOperator.getJobNames() does only return Names of Jobs that have already been executed since server start

    XMLWordPrintable

Details

    Description

      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?

      Attachments

        Issue Links

          is cloned by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-23107 [GSS](7.4.z) WFLY-15921 - JobOperator.getJobNames() does only return Names of Jobs that have already been executed since server start

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBERET-536 getJobInstances, getJobInstanceCount, getRunningExecutions should include jobs that have not been started

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFLY-15954 getJobInstances, getJobInstanceCount, getRunningExecutions should include jobs that have not been started

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-16112 Batch JobOperatorService should look for only active job names to stop during suspend

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: