ErrorEndEvent is not propagated to parent process

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

joao_p_silva

We have two processes, A and B, where B is a sub-process of A.

In the parent process A, we have an Event Sub-Process with an ErrorStartEvent with Error Code "customError".

In process B, we also have an Event Sub-Process with an ErrorStartEvent with Error Code "customError", but at the end, we re-throw this same error code with an ErrorEndEvent, in order to trigger the Event Sub-Process of the parent process A.

This, however, produces an infinite loop. In other words, instead of propagating the ErrorEndEvent from process B to the parent process A, it keeps processing the error in process B. Making an analogy with Java, what we have is the following:

A() { // Parent Process
  try {
    B();  // Sub Process
  } catch (CustomError e) {  // Event Sub Process ErrorStartEvent
    doSomething();
  }
}

B() {
  try {
    doSomethingElse();
  } catch (CustomError e) { // Event Sub Process ErrorStartEvent
    doYetSomething();
    throw e; // This ErrorEndEvent is never caught by A
  }
}
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

However, the Exception from B never reaches A, it keeps looping in the catch block of B.

martin_grofcik

Hi,

As I  understand error is caught in subprocess B in the event sub-subprocess.

I can  be sure only when I write jUnit test, but what could happen is following:

<br>&nbsp; public static void propagateError(String errorCode, ActivityExecution execution) throws Exception {<br>&nbsp;&nbsp;&nbsp; // find local error handler<br>&nbsp;&nbsp;&nbsp; String eventHandlerId = findLocalErrorEventHandler(execution, errorCode);&nbsp; <br><br>&nbsp;&nbsp;&nbsp; // TODO: merge two approaches (super process / regular process approach)<br>&nbsp;&nbsp;&nbsp; if(eventHandlerId != null) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; executeCatch(eventHandlerId, execution);<br>&nbsp;&nbsp;&nbsp; }else {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ActivityExecution superExecution = getSuperExecution(execution);<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (superExecution != null) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; executeCatchInSuperProcess(errorCode, superExecution);<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } else {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LOG.info("{} throws error event with errorCode '{}', but no catching boundary event was defined. Execution will simply be ended (none end event semantics).",<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; execution.getActivity().getId(), errorCode);<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; execution.end();<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br>&nbsp;&nbsp;&nbsp; }<br>&nbsp; }<br>
org.activiti.engine.impl.bpmn.helper.ErrorPropagation#findLocalErrorEventHandler finds current event subprocess and that's why it ends in endless loop. Your case can be solved by changing error code.

The question is whether it is correct behavior or not.

Regards
Martin