NormalizedMessageImpl should use the ConcurrentHashMap to avoid the
ConcurrentModificationException
----------------------------------------------------------------------------------------------------
Key: SMXCOMP-558
URL: https://issues.apache.org/activemq/browse/SMXCOMP-558
Project: ServiceMix Components
Issue Type: Improvement
Components: servicemix-shared
Reporter: Willem Jiang
Attachments: SMXCOMP-558.patch
Under high load when the timing is just right our camel routes are getting
ConcurrentModificationExceptions. We have tracked this down to
NormalizedMessageImpl.java in servicemix-core. Specifically in the
createPropertiesMap method on line 295. There's a comment that Normalized
exchanges do not need to be thread-safe but we are definitely seeing issues
with this. We changed the use of HashMap to ConcurrentHashMap and do not see
the problem anymore.
Please see more information here
http://fusesource.com/issues/browse/ESB-724
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
