topic Re: Capture all exceptions in ESB route in Talend Studio

Capture all exceptions in ESB route

ravi999 — Sat, 16 Nov 2024 07:23:56 GMT

Hi All,

We are able to send general email using cMail component.But how to send emails for all exceptions in ESB route? I have seen the cOnexception. But not sure what all exceptions(like java.lang.Exception) needs to be added in advanced setting so that all errors can be captured so that email notification can be sent.

Re: Capture all exceptions in ESB route

Anonymous — Sun, 28 Oct 2018 18:01:16 GMT

java.lang.Exception should catch all Exceptions for you. If you want to catch absolutely anything that could be thrown by the Route, you could try using java.lang.Throwable. I've not actually tried this myself, but it should work.

Re: Capture all exceptions in ESB route

ravi999 — Sun, 28 Oct 2018 19:01:54 GMT

No luck. I tried keeping java.lang.Throwable and tried keeping other exceptions in the pic in advanced setting. Here are the errors I generated which are not captured. Not sure if my approach is correct.

Failed to create Producer for endpoint:

org.apache.kafka.common.KafkaException: Failed to construct kafka producer

java.io.FileNotFoundException etc

2018-10-28 14_55_50-Amazon WorkSpaces.png

Re: Capture all exceptions in ESB route

Anonymous — Sun, 28 Oct 2018 21:33:38 GMT

You need to "Handle the Exceptions" to enable this I believe. Unfortunately I cannot test this on my machine at the moment as I don't have ESB on here. But on looking at your screenshot, you have "None" selected for the "Exception Behaviour"

Re: Capture all exceptions in ESB route

ravi999 — Sun, 28 Oct 2018 21:36:33 GMT

I tried by keeping the handle exception as well.

Re: Capture all exceptions in ESB route

Anonymous — Sun, 28 Oct 2018 21:44:53 GMT

What happens when you do that? I am suspicious as to whether the cMail is causing some confusion here. Maybe temporarily replace it with a cProcessor and a simple System.out

Re: Capture all exceptions in ESB route

Anonymous — Sun, 28 Oct 2018 21:49:16 GMT

I've also noticed that you errors are fundamental flaws with your Route. Your route cannot run with those errors. Can you create a route with an intermittent divide by 0 error (or similar)? Something like a cTimer--->cProcessor (with the divide by 0 error) and your cOnException process.

I don't believe the the cOnException component will work very well with fundamental route issues. I believe it will work better for intermittent data errors (in Beans, etc).

Re: Capture all exceptions in ESB route

ravi999 — Mon, 29 Oct 2018 04:45:34 GMT

I assumed cOnexception works like tlogcatcher in DI where it captures some of the errors like Table not found. The solution u suggested to keep 4/0 triggered the cOnexception. But I have one observation, I have the below 3 statements in cprocessor. In this case, 2nd statement threw exception and the 3rd statement is not executed. As soon as there is exception, cOnexception is getting triggered and remaining statements in cprocessor are not getting executed. I observed the sme case with ignore exceptions, handle exceptions , none in conexception component. Is there a way to ignore the exception , keep the route running for next messages and to get email notification for exception so that prod support team can look into the exceptions.

Re: Capture all exceptions in ESB route

Anonymous — Mon, 29 Oct 2018 09:16:04 GMT

I think you have to treat exceptions like you would in a Java try/catch block. As soon as you get an exception within the same try/catch (a single component would behave like this), the catch is initiated and the flow is changed.

Re: Capture all exceptions in ESB route

ravi999 — Sun, 04 Nov 2018 00:30:22 GMT

So in that case. As soon as we get a error, exception will be activated and we get email regarding the exception. Next messages in the queue will not processed. Is there any way to ignore the exception and keep updates flowing, send email in case as soon as the exception is identified ?

Re: Capture all exceptions in ESB route

Anonymous — Sun, 04 Nov 2018 16:01:27 GMT

A problem which means a route is broken (missing endpoint within the same route, etc) will prevent the route from functioning. You should not allow issues like that to get beyond testing. Issues like the divide by 0 error I mentioned above that can be caused by your data, should not crash the route and you should be able to achieve what you have mentioned in your last post.

One thing to keep in mind with routes, you should test them in the Karaf (ESB runtime) and not just the Studio. You will likely see a slightly different behaviour with your errors and how they are handled.