topic Re: Execution doesn't exist in Alfresco Archive

Execution doesn't exist

zaiteki — Mon, 23 Jun 2014 16:19:10 GMT

Hello,I rarely get following exception when running the activiti flowEVERE: exception during timer executionorg.activiti.engine.ActivitiException: Error while evalutaing expression at org.activiti.engine.impl.el.JuelExpression.getValue(JuelExpression.java:59) at org.activiti.engine.i

Re: Execution doesn't exist

martin_grofcik — Tue, 24 Jun 2014 06:27:18 GMT

Hi,

org.activiti.engine.ActivitiException: execution 134401 doesn't exist

Is it possible that process instances has ended between query and get variable?

roll-back functionality

I do not know which event handler you mean.
Could you create jUnit test?

Regards
Martin

Re: Execution doesn't exist

zaiteki — Tue, 24 Jun 2014 08:10:56 GMT

Hello,

I do not know which event handler you mean.

I meant the java code processing flow events, I called it event handler e.g.
<code>
<serviceTask id="Exited" name="Exited" activiti:expression="${events.exited(entityId)}"></serviceTask>
</code>

Is it possible that process instances has ended between query and get variable?

It shouldn't, it is an user task with a timer boundary event attached. The timer moves the flow to the "Exited" state, where it tries to update some variables and fails.

Regards,

Re: Execution doesn't exist

jbarrez — Fri, 04 Jul 2014 09:33:03 GMT

Very strange. The error is thrown when the execution indeed is not in the db … so something is moving the execution forwards.

Do tyou hava an @Transactional around your logic? Otherwise there will be two transactions for the snippet of codeyou posted.

Re: Execution doesn't exist

abhishek1 — Tue, 21 Jul 2015 12:51:28 GMT

I am getting similar error: <code>org.activiti.engine.ActivitiObjectNotFoundException: execution 447505 doesn't exist </code>.

Could anyone clarify on this?

Re: Execution doesn't exist

jbarrez — Thu, 23 Jul 2015 09:33:45 GMT

Not with that little amount of context. I can only tell you that execution 447505 is not there, but it was expected to be there.