Cancel BoundaryEventTimer?

[jonathan1]

I have a process that calls three call activities in Activiti 5.10.  Each call activity has a BoundaryEventTimer associated with it, used if the call activity gets stuck (right now just going to an ErrorEndEvent).

Looking at the Activiti DB and trace of variable assignments, it appears that the BoundaryEventTimer associated with a call activity gets fired (on time) after the call activities have completed, taking the process execution down the path towards handling stuck call activities.

Is there a way to cancel boundary event timers when the associated task completes prior to the timer firing?

I could have the execution following the boundary event check an exit status variable, but I'm wondering if there's a cleaner solution in the XML configuration.

[frederikherema1]

When the scope the timer is on is destroyed (e.g. task completed, subprocess finished), the timers are deleted as well. How does your process XML looks? Maybe you could create a unit-test demonstrating the problem.

[jonathan1]

Thank you, frederikheremans,

I've narrowed down the problem and am waiting on Maven to download resources from the Alfresco Maven Repository through my company's firewall so I can insert the "unit" test into the Activiti unit-test framework on the sticky post…

While I'm waiting… and waiting…  The problem stems from installing a TimerBoundaryEvent on a ReceiveTask used inside a CallActivity.   The ReceiveTask gets signalled, flow proceeds normally, but then the timer on the ReceiveTask is triggered later.