If I replace the multiple-consumer SEDA Queue with a JMS Topic, everything works fine...ie: All three routes get the data.
Is there a known problem with dynamically adding consumers to a multiple-consumer SEDA Queue? I need to do some more digging, but I turned on the Camel debug logging and saw some odd behavior with the size of the thread pool. After adding the 3rd route, it kept switching from a thread pool of size 1 to size 3. I don't know if that had anything to do with the issue I was seeing but it definitely stood out. I'll keep looking into it but if anyone has any insight I would be grateful! -- View this message in context: http://camel.465427.n5.nabble.com/Odd-route-start-behavior-after-context-is-started-tp2835464p2838501.html Sent from the Camel - Users mailing list archive at Nabble.com.
