topic Re: Setting Process Variable after complete: Process does nit finish correctly. in Alfresco Archive

Setting Process Variable after complete: Process does nit finish correctly.

dognose — Mon, 16 Sep 2013 10:20:10 GMT

Hello,We have a process, that finishes with a service task (db update). [img]http://abload.de/img/capturedzrhx.png[/img]In there, we used runtimeService.setVariable(); to set another variable, if the database update was successfull or not.(this method is called by the service task)ublic void updat

Re: Setting Process Variable after complete: Process does nit finish correctly.

frederikherema1 — Fri, 20 Sep 2013 12:35:02 GMT

Do you have an isolated unit-test for this that can be run easily standalone with the configuration you're using? As this is quite trivial behaivour (saving variables), we have a lot of coverage for these kind of things. Could be that a specific configuration OR operation( or the moment you do it) is causing this issue.

Re: Setting Process Variable after complete: Process does nit finish correctly.

aggiepilot04 — Tue, 22 Apr 2014 21:26:39 GMT

We're having a similar issue that seems to be related to ACT-955:

<code>
### Error updating database. Cause: java.sql.SQLIntegrityConstraintViolationException: ORA-02292: integrity constraint (ACTIVITI.ACT_FK_VAR_EXE) violated - child record found

### The error may involve org.activiti.engine.impl.persistence.entity.ExecutionEntity.deleteExecution-Inline
### The error occurred while setting parameters
### SQL: delete from ACT_RU_EXECUTION where ID_ = ? and REV_ = ?
### Cause: java.sql.SQLIntegrityConstraintViolationException: ORA-02292: integrity constraint (ACTIVITI.ACT_FK_VAR_EXE) violated - child record found
</code>

It seems to be related to having duplicate variables in ACT_RU_VARIABLE (note the REV is incremented):

2070893 2 string rootProcessDefinitionKey 1796751 1796751
2068451 1 string rootProcessDefinitionKey 1796751 1796751

After deleting one of these, we can complete the workflows…but I can't figure out how these dups are being created. We use the REST API for all of our Activiti integration. We've also only seen this issue in our production environment, which is 5.14. Any ideas?

Re: Setting Process Variable after complete: Process does nit finish correctly.

aggiepilot04 — Tue, 22 Apr 2014 21:49:22 GMT

Didn't make it all the way through the forum search results before posting…my bad. Looks like this was resolved in 5.15 under ACT-1887. I can't think of any place where we'd update a variable in separate threads, but somehow that is happening. Since the fix is in setting the variables, we'll need to manually delete all of the dups from the table after the upgrade…correct?

Re: Setting Process Variable after complete: Process does nit finish correctly.

jbarrez — Thu, 24 Apr 2014 07:32:34 GMT

> Since the fix is in setting the variables, we'll need to manually delete all of the dups from the table after the upgrade…correct?

Yes, it does seem like it unfortunately.

One thing to verify is that it works on 5.15.1, before doing the production upgrade. especially if you are mentioning that you aren't using multiple threads on the same process

Re: Setting Process Variable after complete: Process does nit finish correctly.

aggiepilot04 — Thu, 24 Apr 2014 18:22:17 GMT

We are planning to change the ACT_FK_VAR_EXE constraint to cascade deletes. Not sure why I didn't think about this before. That should get us up and running on 5.14 without the risk of rushing an upgrade outside of a release cycle, and we also won't have to worry about deleting the dups.

Regarding multipe threads…we are using execution listeners for setting a couple of variables on Start (rootProcessDefinitionKey and rootProcessInstanceId). We use subprocesses/call activities extensively, and as variable names imply, this allows us to see what the base workflow is from the child process. Since both the base workflow and the subprocess use the listener, we may be getting dups if the variable is set on both process instances before the first commit point. The strange thing is that we can't recreate the problem in any pre-production environment (on either 5.14 or 5.15.1). The only way to force the constraint violation is to manually insert the duplicate variables in the table.

Anyways, regardless of how the dups are being set (and whether or not it's fixed in 5.15.1), the cascading delete should resolve the issue. Once we're on 5.15.1 in production, I will check to see if we're still getting runtime variable dups and report back.

Re: Setting Process Variable after complete: Process does nit finish correctly.

jbarrez — Fri, 25 Apr 2014 08:04:38 GMT

> We are planning to change the ACT_FK_VAR_EXE constraint to cascade deletes.

Good thinking.

> Once we're on 5.15.1 in production, I will check to see if we're still getting runtime variable dups and report back.

Great. Looking forward to no dups 🙂

Re: Setting Process Variable after complete: Process does nit finish correctly.

sharat — Sat, 10 May 2014 13:48:47 GMT

Joram,

Can you please confirm if this issue is fixed in 15.5.1 .