[SMXCOMP-558] NormalizedMessageImpl should use the ConcurrentHashMap to avoid the ConcurrentModificationException

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 3.2.4, servicemix-camel-2009.02
• Component/s: servicemix-shared
• Patch Info: Patch Available
• Assignee: Gert Vanthienen
• Reporter: Willem Jiang
• Created: 03/Jun/09 07:38
• Updated: 12/Jun/09 16:57
• Resolved: 12/Jun/09 16:57

Description

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