On Fri, Nov 12, 2010 at 10:22 AM, waterback <mart...@innoq.com> wrote: > > > Claus Ibsen-2 wrote: >> >> Okay I checked the source >> > Thank you... > > Do you have any other idea then, how to control that the route that tries to > connect and is denied by WMQ > is either stopped right away or at least that i could see that it is not > really started, although it declares itself started, when you ask > CamelContext with getRouteStatus(..) >
>From Camel point of view the route was started because the start operation succeeded. You most likely need to use an exception listener on the JMS endpoint/component to catch those exceptions from IBM WebSphere. > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Connect-with-WebSphere-MQ-Single-Consumer-allowed-tp3260184p3261686.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
