Activiti current task behaviour with asynchronous tasks

sdesbure — Fri, 26 Jun 2015 08:10:21 GMT

Hello,I'm using activiti mostly with asynchronous services tasks. The issue is if I "simply" chain these tasks, the current task id (which seems to be relied to act_id_ column in act_ru_execution) is not updated.In order to have this update, I've added a receive task for each asynch service task and

Re: Activiti current task behaviour with asynchronous tasks

martin_grofcik — Mon, 29 Jun 2015 06:50:58 GMT

Hi,

use http://activiti.org/userguide/index.html#_hooking_into_process_parsing to add automatic logging before each service task.

Regards
Martin

Re: Activiti current task behaviour with asynchronous tasks

sdesbure — Mon, 29 Jun 2015 06:55:35 GMT

Hello Martin and thanks for answering.
What you propose is to add an automatic logging service that would for example automatically insert into the database where we are?
Is that right?

Regards,

Sylvain

Re: Activiti current task behaviour with asynchronous tasks

jbarrez — Tue, 30 Jun 2015 20:09:11 GMT

I'm not sure i'm following your use case:

"The issue is if I "simply" chain these tasks, the current task id"

What do you mean? When it's asynchronous, the current state can change _any time_, cause the processing will happen at a later point in the future.

Re: Activiti current task behaviour with asynchronous tasks

sdesbure — Wed, 01 Jul 2015 14:05:32 GMT

Hello,
it wasn't clear I understand
So, here's the issue : I'm using on the same workflow synchronous and asynchronous services tasks.
After passing the asynchronous tasks, the DB (act_id_ row on act_ru_execution table) is updated only on asynchronous tasks which lead to confusion. Here's an example (code can be found on github https://github.com/sdesbure/activiti-issue-asynch-task😞
<code>DEBUG MyUnitTest - starting test
DEBUG MyUnitTest - runtime service: org.activiti.engine.impl.RuntimeServiceImpl@7244001e
DEBUG SyncTask - entering SyncTask
DEBUG SyncTask - active_activiti:
DEBUG SyncTask - * found per execution : firstTask
DEBUG SyncTask - * found via SQL (same as REST request): none
DEBUG SyncTask - finished SyncTask
DEBUG MyUnitTest - processInstance ID: 4
DEBUG AsyncTask - entering AsyncTask
DEBUG AsyncTask - * found per execution : secondTask
DEBUG AsyncTask - * found via SQL (same as REST request): secondTask
DEBUG AsyncTask - finished AsyncTask
DEBUG AsyncTask - entering AsyncTask
DEBUG AsyncTask - * found per execution : thirdTask
DEBUG AsyncTask - * found via SQL (same as REST request): thirdTask
DEBUG AsyncTask - finished AsyncTask
DEBUG SyncTask - entering SyncTask
DEBUG SyncTask - active_activiti:
DEBUG SyncTask - * found per execution : fourthTask
DEBUG SyncTask - * found via SQL (same as REST request): thirdTask
DEBUG SyncTask - finished SyncTask
DEBUG SyncTask - entering SyncTask
DEBUG SyncTask - active_activiti:
DEBUG SyncTask - * found per execution : fifthTask
DEBUG SyncTask - * found via SQL (same as REST request): thirdTask
DEBUG SyncTask - finished SyncTask
DEBUG SyncTask - entering SyncTask
DEBUG SyncTask - active_activiti:
DEBUG SyncTask - * found per execution : sixthTask
DEBUG SyncTask - * found via SQL (same as REST request): thirdTask
DEBUG SyncTask - finished SyncTask
INFO DefaultAsyncJobExecutor - Shutting down the default async job executor [org.activiti.engine.impl.asyncexecutor.DefaultAsyncJobExecutor].</code>

with the following bpmn:
<code><?xml version="1.0" encoding="UTF-8"?>

<definitions xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:activiti="http://activiti.org/bpmn"
             xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlnsmgdc="http://www.omg.org/spec/DD/20100524/DC"
             xmlnsmgdi="http://www.omg.org/spec/DD/20100524/DI" typeLanguage="http://www.w3.org/2001/XMLSchema"
             expressionLanguage="http://www.w3.org/1999/XPath" targetNamespace="http://www.activiti.org/test">

    <process id="my-process">

        <startEvent id="start" />
        <sequenceFlow id="flow1" sourceRef="start" targetRef="firstTask" />

        <serviceTask id="firstTask" name="Activiti is awesome! 1" activiti:delegateExpression="${syncTask}" />
        <sequenceFlow id="flow2" sourceRef="firstTask" targetRef="secondTask" />

        <serviceTask id="secondTask" name="Activiti is awesome! 2" activiti:async="true" activiti:delegateExpression="${asyncTask}" />
        <sequenceFlow id="flow3" sourceRef="secondTask" targetRef="thirdTask" />

        <serviceTask id="thirdTask" name="Activiti is awesome! 3" activiti:async="true" activiti:delegateExpression="${asyncTask}" />
        <sequenceFlow id="flow4" sourceRef="thirdTask" targetRef="fourthTask" />


        <serviceTask id="fourthTask" name="Activiti is awesome! 4" activiti:delegateExpression="${syncTask}" />
        <sequenceFlow id="flow5" sourceRef="fourthTask" targetRef="fifthTask" />


        <serviceTask id="fifthTask" name="Activiti is awesome! 5" activiti:delegateExpression="${syncTask}" />
        <sequenceFlow id="flow6" sourceRef="fifthTask" targetRef="sixthTask" />

        <serviceTask id="sixthTask" name="Activiti is awesome! 6" activiti:delegateExpression="${syncTask}" />
        <sequenceFlow id="flow7" sourceRef="sixthTask" targetRef="end" />


        <endEvent id="end" />
    </process>
</definitions>
</code>

the solution one of my colleague found was to add a receives task for each service task which allow the update of the DB but I find this solution very ugly.
I would just want to update the DB for every service task if the row exists and I would like to know what's can be done.

The result I would like to have would be:
<code>DEBUG MyUnitTest - starting test
DEBUG MyUnitTest - runtime service: org.activiti.engine.impl.RuntimeServiceImpl@7244001e
DEBUG SyncTask - entering SyncTask
DEBUG SyncTask - active_activiti:
DEBUG SyncTask - * found per execution : firstTask
DEBUG SyncTask - * found via SQL (same as REST request): none
DEBUG SyncTask - finished SyncTask
DEBUG MyUnitTest - processInstance ID: 4
DEBUG AsyncTask - entering AsyncTask
DEBUG AsyncTask - * found per execution : secondTask
DEBUG AsyncTask - * found via SQL (same as REST request): secondTask
DEBUG AsyncTask - finished AsyncTask
DEBUG AsyncTask - entering AsyncTask
DEBUG AsyncTask - * found per execution : thirdTask
DEBUG AsyncTask - * found via SQL (same as REST request): thirdTask
DEBUG AsyncTask - finished AsyncTask
DEBUG SyncTask - entering SyncTask
DEBUG SyncTask - active_activiti:
DEBUG SyncTask - * found per execution : fourthTask
DEBUG SyncTask - * found via SQL (same as REST request): fourthTask
DEBUG SyncTask - finished SyncTask
DEBUG SyncTask - entering SyncTask
DEBUG SyncTask - active_activiti:
DEBUG SyncTask - * found per execution : fifthTask
DEBUG SyncTask - * found via SQL (same as REST request): fifthTask
DEBUG SyncTask - finished SyncTask
DEBUG SyncTask - entering SyncTask
DEBUG SyncTask - active_activiti:
DEBUG SyncTask - * found per execution : sixthTask
DEBUG SyncTask - * found via SQL (same as REST request): sixthTask
DEBUG SyncTask - finished SyncTask
INFO DefaultAsyncJobExecutor - Shutting down the default async job executor [org.activiti.engine.impl.asyncexecutor.DefaultAsyncJobExecutor].</code>

Re: Activiti current task behaviour with asynchronous tasks

martin_grofcik — Fri, 03 Jul 2015 06:39:48 GMT

yes.
You have to take into account transactions too. (That's the reason why HI tables update is not seen from outside.)

Regards
Martin

topic Re: Activiti current task behaviour with asynchronous tasks in Alfresco Archive

Activiti current task behaviour with asynchronous tasks

Re: Activiti current task behaviour with asynchronous tasks

Re: Activiti current task behaviour with asynchronous tasks

Re: Activiti current task behaviour with asynchronous tasks

Re: Activiti current task behaviour with asynchronous tasks

Re: Activiti current task behaviour with asynchronous tasks