topic Re: MI User task followed by a Service Task in Alfresco Archive

MI User task followed by a Service Task

luisalves00 — Wed, 02 Oct 2013 09:03:58 GMT

Hello,Part of my workflow goes like this:<blockcode> <userTask id="Auth-Request-Program" name="Program Auth (${requestN} / ${programmerGroupItem.name})" activiti:candidateUsers="${programmerGroupItem.programadores}"> <extensionElements>

Re: MI User task followed by a Service Task

frederikherema1 — Wed, 02 Oct 2013 10:25:46 GMT

If execution of the servicetask6 fails, the transaction will be rolled back, leaving the state of the process still in "user task" waiting to be completed…

Re: MI User task followed by a Service Task

luisalves00 — Wed, 02 Oct 2013 13:34:49 GMT

well…I got it stuck on servicetask6 (in fact is another path so is a servicetask5)…

so I think the behaviour is this:

<blockcode>
tx.begin()
    servicetask6
tx.commit()

tx.begin()
    servicetask7
    [throw exception…tx.rollback() ]
tx.commit()
</blockcode>

the process is now "blocked"….on the table activiti.act_ru_execution

Act_id_ = servicetask6
is_Active_ = 1
is_Scope_ = 1

So how can I get the process running again?

Re: MI User task followed by a Service Task

luisalves00 — Wed, 02 Oct 2013 13:39:21 GMT

tks..what a quick answer.

even if I got a following servicetask7? i.e. userTask –> servicetask6 –> servicetask7

If servicetask7 fails, I get back to the userTask, right?

(still using engine 5.7)

Re: MI User task followed by a Service Task

frederikherema1 — Thu, 03 Oct 2013 07:51:00 GMT

Is the servicetask7 or servicetask6 marked as async?

Re: MI User task followed by a Service Task

luisalves00 — Thu, 03 Oct 2013 08:15:08 GMT

No. Using the default settings.

I've tested the code using a break point on the servicetask7 and changing a variable value to get a NPE.
The flow rollbacked to the UserTask, so you must span the transactions (as I expected).
But something went wrong, at least in 3 cases, where the flow blocked at servicetask6. This makes any sense?
Is there a way to signal the flow to keep going?

tks.

LA

Re: MI User task followed by a Service Task

frederikherema1 — Wed, 09 Oct 2013 12:25:28 GMT

You SHOULD NOT commit transactions manually in between 2 non-async steps (like the service-tasks). This will cause the engine to fail to roll-back to the previous state (== previous wait state before servicetask6). Since the transaction is commited by you after servicetask6, this "trail" is lost forever and it will fail.

To put it simple, NEVER commit transactions during a single API-call!! You can have activiti participate in an external transaction without issues, as long as the transaction spans at least a single API-call.