[
https://issues.apache.org/jira/browse/CAMEL-12727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581023#comment-16581023
]
Claus Ibsen commented on CAMEL-12727:
-------------------------------------
We could synchronize that hack
{code}
// need to synchronize this to avoid concurrency issue
synchronized (this) {
oldExchange = originalExchange.copy();
}
{code}
We could also consider going back to ConcurrentHashMap. The implementation in
newer JVMs are much better now.
> java.util.ConcurrentModificationException at
> org.apache.camel.impl.DefaultExchange.createProperties(DefaultExchange.java:550)
> in 2.20.1
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-12727
> URL: https://issues.apache.org/jira/browse/CAMEL-12727
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.20.0
> Environment: Camel 2.20.1.
> The exception occurs within a aggregation processor using a custom
> aggregation strategy and optimistic locking.
> Reporter: Philippe Bouteleux
> Priority: Major
> Fix For: 2.23.0
>
> Attachments: dih-error.queue_2 (1).txt
>
>
> A concurrent access exception occurs during our load tests while consuming
> messages from a rabbitmq queue.
> The call stack embedded below shows that the issue is related to an
> "optimization" which was introduced in
> https://issues.apache.org/jira/browse/CAMEL-11330 to replace a
> ConcurrentHashMap with a regular one from version 2.19.5 to 2.20.0 onward.
> The faulty code is still present in latest 2.22.0.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
