topic Re: BoundaryTimer sometimes not working in Alfresco Archive

BoundaryTimer sometimes not working

dokmatik — Fri, 19 Oct 2012 10:11:24 GMT

Activiti version is 5.10.Hello everyone,I have a strange issue which itches me lately.Being unable to upload an appropriate image I will try to illustrate my issue with the following (primitive) drawing|————| receiveTask ————>[ex gateway]|————| [boundaryTimer]———–^There is this receive ta

Re: BoundaryTimer sometimes not working

frederikherema1 — Fri, 19 Oct 2012 13:34:55 GMT

A bit more details needed:
- Does the boundary-event cancel the activity?
- Do you actually signal the receiveTask, before it goes wrong?

Re: BoundaryTimer sometimes not working

dokmatik — Fri, 19 Oct 2012 15:17:57 GMT

A bit more details needed:
- Does the boundary-event cancel the activity?
Yes, it does.
- Do you actually signal the receiveTask, before it goes wrong? -
Well, there is some probability a user has signalled the process instance via its frontend. But I havent found anything in my logs and could not find appropriate entries in ACT_HI_ACTINST for activities following [receiveTask] either indicating that the process instance has been continued.

Re: BoundaryTimer sometimes not working

jbarrez — Mon, 22 Oct 2012 08:58:44 GMT

What happens after the signal? Does the process ends? Are there automatic steps following?

Re: BoundaryTimer sometimes not working

dokmatik — Tue, 23 Oct 2012 09:00:24 GMT

After the receiveTask an exclusiveGateway follows as shown in the sketch.
The exGateway has 2 outgoing flows
- one which leads to more activities (but that path is not taken because of failing the given condition)
- second one leading to the process end event (no condition defined for this one)

Since the current instance is called from an outside CallActivity element we should return to the enclosing process instance finally leading to an end event.

Having had a look at my process model again I know realize that my aforementioned ex-gateway does not contain a "Default flow"-setting.
This actually used to be a problem with other exGateways of my process models. I had observed that without a "Default flow"-setting and having set a condition only on single outgoing flow only the instance mysteriously "stopped".
That could be here the case too.

I will fill in the "Default flow"-setting of the exlusive gateway and see what happens.

What do you say ?

Re: BoundaryTimer sometimes not working

jbarrez — Tue, 23 Oct 2012 21:49:22 GMT

It could be that it is indeed the case you need to use a default flow … but if it happens so rarely, it really shouldn't be the default 😉