I'm seeing an issue when starting routes (pulling from a multiple-consumer SEDA Queue) after the context has been started. After the 3rd route is started, the 3rd route does not receive most of the data while the other two routes receive all the data. Am I doing the wrong thing by adding routes after the Camel Context has been started? I was under the impression that I could start/stop routes after the context starts so it must have something to do with my implementation.
I created a simple program to illustrate the problems observed where each route has a processor that simply prints the message to the screen and keeps a count of the messages it has seen. Here's a summary of what I'm doing: 1. Start a route that takes data off a SEDA Queue and send to a SEDA multiple-consumer Queue 2. Start route 'r1' that pulls data from the multiple consumer queue 3. Send 10 messages. RESULT: Route 'r1' receives all 10 messages 4. Start route 'r2' that pulls data from the mutliple consumer queue 5. Send 10 messages. RESULT: Route 'r1' and 'r2' each receive all 10 messages 6. Start route 'r3' that pulls data from the multiple consumer queue 7. Send 10 messages RESULT: Routes 'r1' and 'r2' each receive all 10 message, 'r3' only receives 1 message To summarize, after adding three routes over a period of time, the last route added does not receive most of the data. The odd thing is that if I start all the routes after starting the context and send them data, all the routes get all messages. It's definitely something to do with the routes being started sequentially...is it something I'm doing wrong? Thanks, Glenn -- View this message in context: http://camel.465427.n5.nabble.com/Odd-route-start-behavior-after-context-is-started-tp2835464p2835464.html Sent from the Camel - Users mailing list archive at Nabble.com.
