I logged a ticket to improve sjms-batch. However for sjms its more
tricky. And also mind that each JMS client may have their own error
handling / failover et all.
https://issues.apache.org/jira/browse/CAMEL-10615
On Sat, Dec 17, 2016 at 4:03 PM, Claus Ibsen <claus.ib...@gmail.com> wrote:
> Not all components support the bridge error handler.
>
> As said its component specific, and some special ones like the JMS
> based do not as they have their own JMS client code / logic and how
> errors is dealt with.
>
> Often they have failover / retry options in the JMS client, eg
> ActiveMQ has some special options etc. IBM WebSphere may have some
> etc.
>
> On Sat, Dec 17, 2016 at 1:43 PM, sa_james <sa_remin...@hotmail.com> wrote:
>> So I went back and read the book again, but it does not show how to handle
>> exception outside of the routing engine. I check the file consumer example
>> and tried to apply it, but it did not work. This is what I did:
>>
>> /onException(classOf[Exception]).to("log:was-caught ${body}")
>>
>> from("batch-sjms:test.foo?consumer.bridgeErrorHandler=true").to("log:test")/
>>
>> I was excepting an IOException (First ConnectException and Subsequent
>> DisconnectException) to be caught, but that was not the case.
>> What am I missing?
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Catching-Exception-tp5791552p5791630.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
