This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new a0e6470 CAMEL-15628: Fixed ArrayIndexOutOfBoundsException for
concurrent / high throughtput routing with message history enabled.
a0e6470 is described below
commit a0e647032386db056cca2dd91346a9626df2ea2b
Author: Claus Ibsen <[email protected]>
AuthorDate: Sat Oct 3 14:18:34 2020 +0200
CAMEL-15628: Fixed ArrayIndexOutOfBoundsException for concurrent / high
throughtput routing with message history enabled.
---
.../src/main/docs/modules/eips/pages/message-history.adoc | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/message-history.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/message-history.adoc
index 43cb853..8d35000 100644
---
a/core/camel-core-engine/src/main/docs/modules/eips/pages/message-history.adoc
+++
b/core/camel-core-engine/src/main/docs/modules/eips/pages/message-history.adoc
@@ -11,12 +11,10 @@ image::eip/MessageHistory.gif[image]
Attaching a Message History to the message will provide a list of all
applications that the message passed through since its origination.
-The message history is disabled by default (to optimize for lower footprint
out of the box). You should only enable message history
+IMPORTANT: The message history is disabled by default (to optimize for lower
footprint out of the box). You should only enable message history
if needed, such as during development, where Camel can report route
stack-traces when a message failed with an exception.
-But for production usage, then message history should only be enabled if you
have monitoring systems that rely on gather these
-fine grained details.
-
-IMPORTANT: When message history is enabled then there is a slight performance
overhead as the history data is stored
+But for production usage, then message history should only be enabled if you
have monitoring systems that rely on gathering these
+fine grained details. When message history is enabled then there is a slight
performance overhead as the history data is stored
in a `java.util.concurrent.CopyOnWriteArrayList` due to the need of being
thread safe.
== Enabling or disabling Message History
