topic Re: Problem with multi-instance sub-process in Alfresco Archive

Problem with multi-instance sub-process

dwoodbury — Thu, 30 Jun 2011 05:49:13 GMT

Hellooes the activiti engine support the attached process definition?I receive the following error when boundary event timers expire within the multi-instance sub-process:2011-06-29 22:30:32,681 [pool-1-thread-18] ERROR interceptor.CommandContext - Error while closing command contextorg.activiti.

Re: Problem with multi-instance sub-process

jbarrez — Thu, 30 Jun 2011 08:39:22 GMT

That should just work.

Can you put the failing process in a unit test and create a new jira?

Re: Problem with multi-instance sub-process

dwoodbury — Thu, 30 Jun 2011 16:07:34 GMT

I've not done that before, but I can try. Can you point me to some instructions or examples? I checked the forums but didn't find a thread for newbies with respect to development.

Also, is it a fair assumption on my part that this is likely an issue with the engine? The sub-process runs autonomously in the engine, creating 5 user-tasks, each with a cancel timer. When the timers expire, the engine throws a concurrency exception.

The reason I ask is because I'm thinking the issue has to due with the non-uniqueness of the task and/or timer id.

I thought I could work-around this issue by giving each user-task a unique name, but I couldn't determine how to parameterize the task and timer names with the loopCounter variable. (or other expression)

Is there a way to define the sub-process such that the embedded timer and user tasks are assigned unique ID's?

Thanks again.

Re: Problem with multi-instance sub-process

jbarrez — Mon, 04 Jul 2011 07:45:02 GMT

I've not done that before, but I can try. Can you point me to some instructions or examples? I checked the forums but didn't find a thread for newbies with respect to development.

The examples shipped with the Activiti distribution are all Junit test. So best place to start there


Also, is it a fair assumption on my part that this is likely an issue with the engine? The sub-process runs autonomously in the engine, creating 5 user-tasks, each with a cancel timer. When the timers expire, the engine throws a concurrency exception.

It sure is possible that it is a bug, but that must be confirmed by a failing test case.

Is there a way to define the sub-process such that the embedded timer and user tasks are assigned unique ID's?
Don't worry, all entities in Activiti get a unique (internal) id. So that's unlikely going the be the issue.

Re: Problem with multi-instance sub-process

dwoodbury — Tue, 09 Aug 2011 07:07:17 GMT

Thanks for the help. I created a test case for the above process definition and was able to reproduce the exception. The exception occurs when the task following the boundary event timer is a mail service task. If the following task is a user task, no exception is raised.

The JIRA ticket is ACT-901 at the following link:

http://jira.codehaus.org/browse/ACT-901

Re: Problem with multi-instance sub-process

jbarrez — Wed, 10 Aug 2011 12:51:50 GMT

Thanks!