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

On job restart, running from a given restartpoint, batch exits as COMPLETED without doing nothing, for batch jobs that contain at least one decider

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 1.2.0.Beta1
    • 1.0.2.Final, 1.1.0.Final
    • jberet-core
    • None
    • Hide

      Any batch job restart containing at least one decider on its job elements.

      Show
      Any batch job restart containing at least one decider on its job elements.

      When a job restart is issued, CompositeExecutionRunner class inside method runFromHeadOrRestartPoint(), it tries to find the id of the restart point given by the batch job. While iterating all the available job elements, if a decider is found on the way, the job exits as nothing happened, in a COMPLETED state. This is due to the misplaced break in the decision instance evaluator.

      Patch fix:
      — Remotely Modified (Based On HEAD)
      +++ Locally Modified (Based On LOCAL)
      @@ -73,10 +73,10 @@
      final Decision decision = (Decision) e;
      if (decision.getId().equals(restartPoint))

      { runDecision(decision); - }

      break;
      }
      }
      + }
      } else {
      // the head of the composite job element is the first non-abstract element (step, flow, or split)
      for (final JobElement e : getJobElements()) {

              cfang@redhat.com Cheng Fang
              mkaramanos Michail Karamanos (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: