Error handling of BpmnError exceptions

[galen...@gmail.com]

Hi,

I'm trying to figure out why task retries only occur if a non-BpmnError (e.g. NullPointerException) is thrown from a JavaDelegate. Even if I don't have a boundary catch for the BpmnError, it seems like throwing BpmnError forces an abort of the process, skipping the retries.

Is this expected? I would have thought any type of exception (even BpmnError) would trigger retries.

Thanks,
Galen

[webcyberrob]

Hi Galen,

Ive always considered a BPMN Exception different to a java runtime error. In particular, BPMN Exception seems to be the mechanism for informing the process layer of the exception and thus enabling the process to take a different path. Consider it a mechanism for raising an event into the process layer.

Hence in my architecture, I advocate the following layering/handling

Java Runtime Error -> Retry -> Incident

Business Exception -> BPMN Exception -> Process level Handler

regards

Rob

[Bernd Rücker (camunda)]

+1

--
You received this message because you are subscribed to the Google Groups "camunda BPM users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to camunda-bpm-us...@googlegroups.com.
To post to this group, send email to camunda-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/camunda-bpm-users/4c4c908b-03a9-4802-bf8c-bce27d5ce40e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.