-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop camunda 'route' on camel exception. #49
Comments
How did you configure the route? See this example where I map Exceptions to a BPMN Error, so I can use it there: Or do you want to create an incident in Camunda? |
Hi. Thanks for your quick response. I made a quick example below displaying my issue. I have two processes in my BPMN. I want Camunda not to run/enter the second process if the first process (a call to camel) throws an exception. I have tried appending the code in your example (adding the onException-snippet to one route, both routes and making it global; also tried to add 'route stop' to the onException clause). It still calls the second process and prints "Got here. Shouldn't have". Java code:
|
Is there something wrong with my solution? Or have I misunderstood how Camunda is supposed to handle these situations? |
Hi! I have tried googling around for a solution to this, but I've not found anything so far.
I'm sending data from Camel to Camunda via
camunda-bpm://start?...
. At several points it calls Camel endpoints, such as${camel.sendTo('direct:debug')}
. However, when any of these Camel routes/endpoints throw an exception, the Camunda route proceeds as if nothing wrong has occurred. This will cause issues later in the Camunda route. Setting an 'exception' variable and checking for it after every call to Camel will make the BPMN extremely bloated real quick.So, in short: Is it possible to cancel a Camunda 'route/run' when one of its calls to Camel throws an exception?
The text was updated successfully, but these errors were encountered: