Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-5086

[GSS] (6.4.z) initial delay is not set for the first executor thread

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 6.4.9
    • 6.4.7
    • jBPM Core

    Description

      Executor initial delay, set like this:

      <property name="org.kie.executor.initial.delay" value="10000"/>
      

      is not set for the first executor thread, see:

      https://github.com/kiegroup/jbpm/blob/master/jbpm-services/jbpm-executor/src/main/java/org/jbpm/executor/impl/ExecutorImpl.java#L231-L240

      this is because 'delayIncremental' is 0 during the first iteration.

      Corresponding log:

      10:45:29,771 DEBUG [org.jbpm.executor.impl.ExecutorImpl] (ServerService Thread Pool -- 54) Starting executor thread with initial delay 2000 interval 3000 and time unit MILLISECONDS
      10:45:29,772 DEBUG [org.jbpm.executor.impl.ExecutorImpl] (ServerService Thread Pool -- 54) Starting executor thread with initial delay 12000 interval 3000 and time unit MILLISECONDS
      10:45:29,773 DEBUG [org.jbpm.executor.impl.ExecutorImpl] (ServerService Thread Pool -- 54) Starting executor thread with initial delay 22000 interval 3000 and time unit MILLISECONDS
      10:45:29,773 DEBUG [org.jbpm.executor.impl.ExecutorImpl] (ServerService Thread Pool -- 54) Starting executor thread with initial delay 32000 interval 3000 and time unit MILLISECONDS
      10:45:29,773 DEBUG [org.jbpm.executor.impl.ExecutorImpl] (ServerService Thread Pool -- 54) Starting executor thread with initial delay 42000 interval 3000 and time unit MILLISECONDS
      

      Attachments

        Issue Links

          Activity

            People

              swiderski.maciej Maciej Swiderski (Inactive)
              rhn-support-mputz Martin Weiler (Inactive)
              Marian Macik Marian Macik
              Marian Macik Marian Macik
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: