ReceiveTask with TimerBoundaryEvent strange behavior !

[meditel]

Hi,

[attachment=1]MyProcess3.png[/attachment]

In this example ReceiveTask is waiting for an external Signal before the timer expiration (20s).
Signal received ScriptTask prints out "Signal received"
Timer expired ScriptTask prints out "Timer expired"

If i execute this process and after 20s i can see the message "Timer expired".
But if i execute this process and send a Signal to the ReceiveTask like this :

…. 
runtimeService.signal(execution.getId());‍‍

then i don't see any message, and i can see that the process has well ended (My instances).

Could someone explain this behavior please ?
Might be a bug ?

Best regards,
Meditel

[meditel]

Seems to be a bug !
Shall i open a Jira for this ?

BR,
Meditel

[trademak]

Hi,

How did you test this? Did you also deploy it on the Activiti Explorer for example?

Best regards,

[meditel]

Hi,

Yes I deployed the process into Explorer and then started it.
If you wait 20s you will see "Timer expired" printed out in Tomcat logs and the process is then ended.
If you start again the process and send a Signal before 20s, then the process is ended but the message "Signal received" is not printed out !

Could you please test it and confirm this behavior ?

BR,
Meditel

[frederikherema1]

Can you create a junit-test for this so we can verify it easily?

[meditel]

Hi,

My apologizes, this is not a bug.
The 'Signal received' message is indeed not printed out in the tomcat console, but it is printed  in the Eclipse one, and this is normal as i have sent the signal from an Eclipse project.

BR,
Meditel