[
https://issues.apache.org/jira/browse/CAMEL-12727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16579559#comment-16579559
]
Philippe Bouteleux edited comment on CAMEL-12727 at 8/14/18 10:22 AM:
----------------------------------------------------------------------
So. I added a custom 'NullAggregationRepository' to my route which is a copy of
the original MemoryAggregationRepository to avoid the internal copy of the
exchange. I will unfortunately only have a result when our perf platform is
ready to upgrade.
I'll give back more information ASAP.
Note that I couldn't avoid the in-memory cache of the exchanges in the
repository without breaking the internal logic of the aggregator.
was (Author: boutblock):
So. I added a custom 'NullAggregationRepository' to my route which is a copy of
the original MemoryAggregationRepository to avoid the internal copy of the
exchange. I will unfortunately only have a result when our perf platform is
ready to upgrade.
I'll give back more information ASAP.
Note that I could avoid the in-memory cache of the exchanges without breaking
the internal logic of the aggregator.
> 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
> 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)
