topic Re: Boundary Error Event on SubProcess not cancelling signal in Alfresco Archive

Boundary Error Event on SubProcess not cancelling signal

mhanrahan — Wed, 14 Jan 2015 02:36:06 GMT

Hi,As part of our process, we have an inclusive gateway that branches to a Signal Catch Event as well as to a Call Activity. In normal execution, the child process will signal the parent process and continue on to another inclusive gateway that will continue when both branches are complete.However,

Re: Boundary Error Event on SubProcess not cancelling signal

jbarrez — Fri, 16 Jan 2015 11:47:01 GMT

No, the signal should be removed in that case.

Can you make a simplified unit test that still shows the problem? That would help us tremendously in fixing it!

Re: Boundary Error Event on SubProcess not cancelling signal

mhanrahan — Mon, 19 Jan 2015 00:22:23 GMT

This example should reproduce the problem.

Re: Boundary Error Event on SubProcess not cancelling signal

jbarrez — Wed, 21 Jan 2015 16:20:11 GMT

Hmm this looks like a real bug. I thought that, if i switched the seq flow so that the signal wait would be done first, tht it would work (due to the way activiti leaves a gateway), but it doesn't. It seems deeper than that.

Does it also happens when there is a wait state first in the call activity (eg a usertask BEFORE the throw error), which is then completed first?

Re: Boundary Error Event on SubProcess not cancelling signal

mhanrahan — Thu, 22 Jan 2015 05:40:43 GMT

Attached I have added another test case for this scenario.

Re: Boundary Error Event on SubProcess not cancelling signal

mhanrahan — Tue, 03 Feb 2015 00:47:18 GMT

Has there been any progress on your side of things for this issue?

If not, has there been an issue raised? ( I can create one, I just need to know there isn't one already there so there aren't duplicates)

Re: Boundary Error Event on SubProcess not cancelling signal

jbarrez — Mon, 09 Feb 2015 19:08:33 GMT

No, no progress. Did you respond to my question

> Does it also happens when there is a wait state first in the call activity (eg a usertask BEFORE the throw error), which is then completed first?

I'm guessing it has to do with the fact that the signal is immediately after reaching the subprocess is fired. Hence why adding wait states would shed light on the issue.

Re: Boundary Error Event on SubProcess not cancelling signal

mhanrahan — Mon, 09 Feb 2015 22:00:44 GMT

Yes, it still happens after a wait state (And I posted an updated Test Case to allow you to reproduce that scenario)