topic Re: HistoricVariableInstanceEntity was updated by another transaction in Alfresco Archive

HistoricVariableInstanceEntity was updated by another transaction

texens — Sat, 09 Aug 2014 18:56:36 GMT

I'm getting the following error when I submit form data.URL : /service/form/form-dataMethod : POSTPayload : {"taskId":"124104","properties":[{"id":"businessName","value":"10123"}, <a lot of other variables go here>]}Response :{errorMessage: "HistoricVariableInstanceEntity[id=124016, name=testU

Re: HistoricVariableInstanceEntity was updated by another transaction

frederikherema1 — Mon, 11 Aug 2014 07:52:29 GMT

Can you share the service-task code you're using?

Re: HistoricVariableInstanceEntity was updated by another transaction

sathish1 — Mon, 11 Aug 2014 14:09:47 GMT

Not sure why are you doing this code.,
<code>
@Override
public void execute(DelegateExecution execution) {

// loginMobileNumber is taken as input in the preceding user task
execution.setVariable(process(execution.getVariable("loginMobileNumber")));

}
</code>

But if you are trying to set a variable you already have the variable in the execution object?? But this still does not prove the theory of why you get an optimistic lock exception I guess.

Cheers.

Re: HistoricVariableInstanceEntity was updated by another transaction

texens — Mon, 11 Aug 2014 14:16:22 GMT

HI frederikheremans,

Thanks for the reply.

The service task code is as mentioned below. I might have found the issue, currently I'm trying to validate my hypothesis.

In my user task, I take an input "loginMobileNumber" from the user. In the service task that follows this user task (user task `Registration User Task` –> Service Task `RegistrationValidator`) , I do some processing on this variable - "loginMobileNumber" and set it to this new modified value in the service task.
The flow is something like this :

User Task `Registration` –> take input "loginMobileNumber" from user (via REST API) –> `RegistrationValidator` Service Task (get the variable value from loginMobileNumber, process it, and then update the variable using - execution.setVariable()

I'm guessing, when I try to update the same variable twice - once as part of user task form submission, and then as part of the service task variable update, I'm running into the optimistic locking exception because the revision of the variable - loginMobileNumber is different for the two of them. Now, on commit, the user task writes to disk first and updates the revision number. Next, the service task is trying to write to disk, but the revision has already been updated by the user task (increased by 1). So, this results in the optimistic locking exception.

Could you please confirm or refute this hypothesis.

— USER TASK —

<userTask id="Registration" name="Registration">
      <extensionElements>
        <activiti:formProperty id="loginMobileNumber" name="Login Mobile Number" type="string" required="true"></activiti:formProperty>
      </extensionElements>
</userTask>

— SERVICE TASK —

public class RegistrationValidator implements JavaDelegate {

@Override
public void execute(DelegateExecution execution) {

    // loginMobileNumber is taken as input in the preceding user task
    execution.setVariable("loginMobileNumber", process(execution.getVariable("loginMobileNumber")));

}

public String process(String loginMobileNumber) {
    // process mobile number
    return processedMobileNumber;
}

EDIT : fixed the setVariable line
-    execution.setVariable(process(execution.getVariable("loginMobileNumber")));
+    execution.setVariable("loginMobileNumber", process(execution.getVariable("loginMobileNumber")));

Re: HistoricVariableInstanceEntity was updated by another transaction

texens — Mon, 11 Aug 2014 14:20:13 GMT

Hi Sathish,

There was a typo in my earlier post.
- execution.setVariable(process(execution.getVariable("loginMobileNumber")));
+ execution.setVariable("loginMobileNumber", process(execution.getVariable("loginMobileNumber")));

I'm taking the loginMobileNumber as input, and then have a function that processes it (say, to remove country code or preceding 0s) and then I save it to the variable. We can look at it as validation of user input.