I have a Spring DSL (camel 2.15) that does a multi-cast by executing a "loop", and firing off other routes using SEDA with the waitForTaskToComplete=never option. There is an Exchange "property" in the exchange that is a DOM object. I've found that in the sub-routes fired off by SEDA, the Exchange is holding the SAME object instances as the original Exchange. This means occasionally we get NPEs because DOM objects aren't thread-safe. At least, this is what it looks like to me. I had the idea that Camel would create a new Exchange objects for the routes started via SEDA and new instances of objects it references. This doesn't appear to be true, at least for properties. Is this correct? Are there sub-objects (like the Message object, Header objects etc) that are cloned into the new Exchange, or are all the sub-objects under the Exchange passed as-is? Thanks clint
-- View this message in context: http://camel.465427.n5.nabble.com/Non-threadsafe-objects-in-multi-casted-exchanges-problem-tp5783803.html Sent from the Camel - Users mailing list archive at Nabble.com.
