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

Stop job execution with STARTING status before it's actually started

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 1.3.0.Final
    • 1.3.0.Beta7
    • jberet-core
    • None

    Description

      If a job execution is in STARTING status (e.g., wait for threads to be available), and the job execution is requested to stop, the job execution should not be actually started running; and the batch status should eventually be updated to STOPPED.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-9610 Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution

          • 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: