topic Re: ActivitiException: this activity doesn't accaccept signals' in Alfresco Archive

ActivitiException: this activity doesn't accaccept signals'

shrinivas_mujum — Wed, 27 Mar 2013 14:12:46 GMT

Activiti Error: Signal receive task after a parallel gateway results in "ActivitiException: this activity doesn't accept signals".Please see the attached process flow diagram.Consider two workflows after receive task,Flow 1: ReceiveTask2->ServiceTask2Flow 2: Call Activiti (this also has a wait ta

Re: ActivitiException: this activity doesn't accaccept signals'

frederikherema1 — Wed, 27 Mar 2013 14:18:10 GMT

When a parallel gateway is reached, depending on the number of outgoing flows, there are additional executions created. In some cases, when a child-execution is closed or created, we do some additional magic to reuse/prune execution. If I'm not mistaken, of there is only one child left, it's possible that the last remaining execution (the one holding the signal) is actually replaced by the parent one, having a different execution-id. I can be mistaken, but I know there is some execution-logic related to this kind of use case.

How do you find out the execution-id you need, prior to calling the signal?

Re: ActivitiException: this activity doesn't accaccept signals'

shrinivas_mujum — Wed, 27 Mar 2013 14:28:50 GMT

So do you want to suggest that, it's a known Activiti issue.

Thanks,
Shriniwas

Re: ActivitiException: this activity doesn't accaccept signals'

frederikherema1 — Wed, 27 Mar 2013 14:29:46 GMT

Again, how do you get the execution-id you want to signal?

Re: ActivitiException: this activity doesn't accaccept signals'

shrinivas_mujum — Fri, 29 Mar 2013 12:40:29 GMT

When the process is started we store the execution id in database and after parallel gateway we use the same execution id to signal Flow 1 -> ReceiveTask2 (2nd waiting task) as its a same process.

Re: ActivitiException: this activity doesn't accaccept signals'

frederikherema1 — Fri, 29 Mar 2013 12:54:44 GMT

Currently, signaling is done on an execution-level and does not cascade down to child-executions. This is done because it's possible that in a single process-instance, multiple parallel paths are active and contain a receive-task that is waiting for a signal.

I'm afraid you'll have to dig down the execution-tree to find out what execution the receive-task -you're interested in- is waiting in.

Re: ActivitiException: this activity doesn't accaccept signals'

shrinivas_mujum — Fri, 29 Mar 2013 13:33:22 GMT

Ok. Thanks for the reply.