From e19321d830e74d399902172783544a49a17c0400 Mon Sep 17 00:00:00 2001 From: Stephan Pelikan Date: Wed, 13 Dec 2023 07:35:03 +0100 Subject: [PATCH] Update READMEs to reflect Camunda version used --- spring-boot/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/spring-boot/README.md b/spring-boot/README.md index cc926aa..38a655f 100644 --- a/spring-boot/README.md +++ b/spring-boot/README.md @@ -35,12 +35,12 @@ If you want a certain version of Camunda (either community or enterprise edition org.camunda.bpm.springboot camunda-bpm-spring-boot-starter - 7.17.6-ee + 7.20.1-ee org.camunda.bpm.springboot camunda-bpm-spring-boot-starter-webapp-ee - 7.17.6-ee + 7.20.1-ee org.camunda.community.vanillabp @@ -150,7 +150,7 @@ vanillabp: ## Job-Executor -The Camunda job-executor is responsible for processing asynchronous continuation of BPMN tasks. It has a delay due to polling the database for jobs (see [Backoff Strategy](https://docs.camunda.org/manual/7.18/user-guide/process-engine/the-job-executor/#backoff-strategy)). If there is manual interaction to the process-engine (e.g. process started, message correlated or user-task completed) you want asynchronous tasks to be completed as soon as possible. For example, you want to give feedback in the UI of a "validation" task following a user-task. Therefore, this adapter wakes up the job-executor to check for new jobs after a manual interaction's transaction is completed. +The Camunda job-executor is responsible for processing asynchronous continuation of BPMN tasks. It has a delay due to polling the database for jobs (see [Backoff Strategy](https://docs.camunda.org/manual/7.20/user-guide/process-engine/the-job-executor/#backoff-strategy)). If there is manual interaction to the process-engine (e.g. process started, message correlated or user-task completed) you want asynchronous tasks to be completed as soon as possible. For example, you want to give feedback in the UI of a "validation" task following a user-task. Therefore, this adapter wakes up the job-executor to check for new jobs after a manual interaction's transaction is completed. In cloud environments one typically wants to free resources in idle times to not waste money (at protect the environment :deciduous_tree:) since resources are charged by time of usage. Camunda's job-executor using a polling strategy to find new jobs which either keeps the database in use or introduces huge delays of execution if max-delays are set to big values. This Camunda 7 VanillaBP adapter alters this behavior by keeping the Job-Executor sleep until the next timed job's due-date (e.g. timer-event). In conjunction with waking up the job-executor in case of manual interaction this helps to minimize database usage. @@ -167,6 +167,6 @@ However, if enabled you have to [set a DB index](https://docs.camunda.org/manual > VanillaBP's job-executor is using `jobExecutorPreferTimerJobs=true` > and `jobExecutorAcquireByDueDate=true`. Please add DB-index according -> to https://docs.camunda.org/manual/7.6/user-guide/process-engine/the-job-executor/#the-job-order-of-job-acquisition +> to https://docs.camunda.org/manual/7.20/user-guide/process-engine/the-job-executor/#the-job-order-of-job-acquisition *Hint:* This feature requires to enable Spring Boot's scheduled tasks [as described here](https://www.baeldung.com/spring-scheduled-tasks#enable-support-for-scheduling).