Thank you. Looking at the tst helped us resolving the issue.
-
Alireza Salemi
--
View this message in context:
http://camel.465427.n5.nabble.com/Exception-doesn-t-get-caught-in-the-route-tp5733381p5734234.html
Sent from the Camel - Users mailing list archive at Nabble.com.
If you also use an errorHandler, you should share this code as well. And as
for every request, you should tell us which Camel version do you use...
I suggest to have a look at [1] where we have 50+ OnException tests. Some
with an errorHandler, some without...
[1]
https://fisheye6.atlassian.com/bro
Hi Ali,
The route based exceptions are working fine for us, following is the
example. Not sure but I have a suggestion for you, can you try catching a
generic Exception, it may be due to different exception being raised.
VoltException
Hi Claus,
We put the exception after and tried it with inheritErrorHandler true
and false. It seems the exception are not caught by the onException clause.
If we add an errorhandler to the route then the exception get caught by the
errorhandler. We specified retries on the errorhandler but the r
should be after . And the option
inheritErrorHandler="false" should be removed.
On Wed, May 29, 2013 at 1:13 AM, salemi wrote:
> Hi All,
>
> we throw an exception in the gsInterface bean but the exception never get
> caught by the onException clause in the route below.
>
> What am I doing wrong
Hi All,
we throw an exception in the gsInterface bean but the exception never get
caught by the onException clause in the route below.
What am I doing wrong here?
Thanks,
Ali
org.springframework.dao.DataAccessExcep
