Suspended definition with signal start event blocks active one with same event

1

I have two definitions that have the same signal start event.

I suspend one of them and I trigger the signal event.

Result: no one of them creates process instances, not even the active one.

I debugged the code and find out that at handleEvent method of SignalEventHandler, an exception is thrown if a definition is suspended, so I guess a rollback is done for my active definition which has started the process instance.

Is there any way to avoid them? I cannot use different signal names.

2

Hi,

Interesting. Your description makes sense.

Yes. :slight_smile: The pull request is only one of them.

Regards

Martin

3

Hey @desp.kaz,

Can you please share with us how you are triggering the signal? Are you using one of the RuntimeService.signalEventReceived that do not take execution id?

@martin.grofcik, I’ve provided a feedback on the pull request. The pull request now silently ignores signals received from any location. That’s not correct.

Cheers,
Filip

4

I would not say so. If the definition is suspended, the exception is not thrown.

The check in EventSubscription.xml checks the execution for suspension but not definition. May be it makes sense to add it there instead.