topic Re: ACT_HI_ACTINST inconsistent with ACT_HI_VARINST in Alfresco Archive

ACT_HI_ACTINST inconsistent with ACT_HI_VARINST

jorell — Wed, 19 Mar 2014 01:07:13 GMT

I have the following bpmn:<?xml version="1.0" encoding="UTF-8"?><definitions id="definitions" targetNamespace="testloop" xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.

Re: ACT_HI_ACTINST inconsistent with ACT_HI_VARINST

jorell — Thu, 20 Mar 2014 20:44:01 GMT

Anyone? Please let me know if it doesn't make sense or if I can provide more info on this. From the looks of it seems like a bug in activiti but I would like someone more experienced to comment on it.

Re: ACT_HI_ACTINST inconsistent with ACT_HI_VARINST

jbarrez — Mon, 24 Mar 2014 13:30:54 GMT

From the stacktrace, isee you are doing a signal:

<code>
at org.activiti.engine.impl.RuntimeServiceImpl.signal(RuntimeServiceImpl.java:192)
</code>

A signal is always on the RUNTIME data, never on ACT_HI_VARINST nor on ACT_HI_ACTINST

Re: ACT_HI_ACTINST inconsistent with ACT_HI_VARINST

jorell — Mon, 24 Mar 2014 20:35:18 GMT

Thanks for your reply. Yes I understand that a signal is on runtime data. I was merely explaining the error that led me to look at the History tables. When I was signaling and I got the error message saying that the execution does not exist, I looked at the history table to see if it ever existed in the past. For the purpose of this thread you may ignore that error message.
My main question is how can an execution exist in ACT_HI_VARINST but not in the ACT_HI_ACTINST. You can view the above queries for specific example of what I mean.

Re: ACT_HI_ACTINST inconsistent with ACT_HI_VARINST

jbarrez — Tue, 01 Apr 2014 18:53:30 GMT

Ok, now i understand your question: what you see here is correct: when the multi instance is entered, child executions are created for each of the instances such that variables can be scoped.

The activity is entered however by the parent of that execution, hence why you see an execution for your variable that is different. It is actually the child of the one which enters the activity.