Loading...

XML

Word

Printable

Story Points:
2
Docs QE Status:
NEW
QE Status:
NEW
Workaround:

Workaround Exists
Workaround Description:
Hide

Set system property "org.kie.executor.timeunit" to "MILLISECONDS"

Do not forget to set related properties. e.g. "org.kie.executor.running.max" to "600000"

In case of jBPM 6, you would also need to set "org.kie.executor.interval" to "3000", "org.kie.executor.initial.delay" to "100000"
Show
Set system property "org.kie.executor.timeunit" to "MILLISECONDS" Do not forget to set related properties. e.g. "org.kie.executor.running.max" to "600000" In case of jBPM 6, you would also need to set "org.kie.executor.interval" to "3000", "org.kie.executor.initial.delay" to "100000"
Git Pull Request:
https://github.com/kiegroup/jbpm/pull/1344

When you use ExecutorServiceImpl.requeue(Long olderThan),

ExecutorServiceImpl converts olderThan (milliseconds) to its timeunit.

ExecutorRequestAdminServiceImpl expects olderThan is milliseconds.

So if you configure ExecutorServiceImpl.timeunit to "SECONDS", "olderThan" is not a correct value. (e.g. 2000 milliseconds to 2 milliseconds)

is incorporated by

RHPAM-1605 ExecutorServiceImpl.requeue(Long olderThan) doesn't calculate a correct value