Looking at DefaultCamelContext a bit its seem clear that its not intended for multi-threaded access. Fortunately, since I use scalaz-camel to define all my routes/endpoints I have a very small api to protect. A quick spike in synchronizing the creation of endpoints -- the only CamelContext mutation that happens in multiples in my app -- seems to have solved my problem.
Ok, now I will stop chatting with myself. -- View this message in context: http://camel.465427.n5.nabble.com/ConcurrentModificationException-added-routes-from-multiple-threads-tp4831653p4832182.html Sent from the Camel - Users mailing list archive at Nabble.com.
