I've temporarily solved the issue by setting the "streaming" property to "true" on the @RecipientList annotation in the dynamic router I'm using.
I've tested this case in my live application and it works fine, but I was wondering what impact, if any, this might have elsewhere. From what I understand, setting the streaming property to true allows the sending of the messages out of order when sending to multiple destinations at once. The default is to serialize the sending and break when an error occurs (i.e. order matters)? Since I'm only sending to one destination ever it doesn't seem like I should care about this property, but the default behavior seems flawed in this scenario when dealing with the try/catch. Should this be filed as a bug or is this intentional? -- View this message in context: http://camel.465427.n5.nabble.com/Issue-with-doTry-doCatch-not-routing-correctly-tp5720325p5720481.html Sent from the Camel - Users mailing list archive at Nabble.com.
