Hi Costa, Yes you are correct, what you are looking at is what I have described in my post where I say "Tonight I also tried to separate the routes out into different route contexts but it didn't change anything".
I've found the way I have structured it with multiple route contexts a bit more convenient because I can easily comment out a route context in the camel context. Nevertheless the behavior between what you are looking at and what I posted on stack overflow is exactly the same. The application works well if I have two routes (i.e. two sets of select inserts) but as soon as I add a third the behavior changes and rather than the first route executing and then finishing and tries to execute it multiple times leaving naturally me with errors on a primary key. Does the way I have defined the root look okay? I will try with Derby but it's not realistic for me. I need to be connecting to sql server and mysql. thanks -- View this message in context: http://camel.465427.n5.nabble.com/SQL-component-issue-infinite-loop-tp5739486p5739788.html Sent from the Camel - Users mailing list archive at Nabble.com.
