-
Bug
-
Resolution: Done
-
Major
-
6.4.7
Executor initial delay, set like this:
<property name="org.kie.executor.initial.delay" value="10000"/>
is not set for the first executor thread, see:
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
- clones
-
RHPAM-360 initial delay is not set for the first executor thread
- Closed