You can use the bridge error handler on the consumer. See details at http://camel.apache.org/why-does-my-file-consumer-not-pick-up-the-file-and-how-do-i-let-the-file-consumer-use-the-camel-error-handler.html
On Thu, Jan 9, 2014 at 5:00 PM, Christian Posta <[email protected]> wrote: > Take a look at http://camel.apache.org/polling-consumer.html and the > pollingStrategy option. This will work for file/ftp components. > > The JMS component will have its own errorHandler. > http://camel.apache.org/jms.html > > There is no "global exception handler" to handle exceptions outside of > the routes. The components are different, the strategies are > different, and should be handled individually. > > On Thu, Jan 9, 2014 at 6:16 AM, baudoust <[email protected]> wrote: >> Ok I catch the point, we do have the same behaviour in our implementation, >> which is not a good news at all ... >> >> I guess the application server, if any in this case, catch the exception, in >> our case we are runing under websphere and the error appears in the >> websphere log, but not is not catch by our monitoring framework. >> >> I will then be interested by your solution if you do found any. I would go >> in the direction having a class starting the camelcontext and catching >> exception but I am even not sure that something would be thrown at that >> level ... >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/Handling-ConnectException-at-route-startup-tp5745762p5745787.html >> Sent from the Camel - Users mailing list archive at Nabble.com. > > > > -- > Christian Posta > http://www.christianposta.com/blog > twitter: @christianposta -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen Make your Camel applications look hawt, try: http://hawt.io
