You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2024/12/04 14:27:00 UTC
(camel) branch camel-4.8.x updated: Update competing-consumers.adoc (#16445)
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch camel-4.8.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-4.8.x by this push:
new 7148ac06b16 Update competing-consumers.adoc (#16445)
7148ac06b16 is described below
commit 7148ac06b16669b30a36560e46fb948c29b1f203
Author: Philippe Soares <ph...@vizgen.com>
AuthorDate: Wed Dec 4 09:26:55 2024 -0500
Update competing-consumers.adoc (#16445)
---
.../src/main/docs/modules/eips/pages/competing-consumers.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/core/camel-core-engine/src/main/docs/modules/eips/pages/competing-consumers.adoc b/core/camel-core-engine/src/main/docs/modules/eips/pages/competing-consumers.adoc
index 65e0a8f2de2..0e122d97638 100644
--- a/core/camel-core-engine/src/main/docs/modules/eips/pages/competing-consumers.adoc
+++ b/core/camel-core-engine/src/main/docs/modules/eips/pages/competing-consumers.adoc
@@ -175,6 +175,6 @@ And when this thread finishes, it will take care of the file completion strategy
into the backup folder. This is an important note that the on completion is done by the asynchronous thread.
This ensures the file is not moved before the file is processed successfully. Suppose the `calculateBean` bean
-could not process one of the files. If it was the asynchronous thread that should do the on completion strategy,
+could not process one of the files. If it was the synchronous thread that should do the on completion strategy,
then the file would have been moved to early into the backup folder. By handing over this to the asynchronous
thread, we do it after we have processed the message completely