3 Replies Latest reply on Nov 28, 2011 7:14 PM by jmorr003

BPM process stops after Human Task in 0.3.0.CR1

jmorr003 Nov 24, 2011 6:56 PM

Locally I am not able to get the switchyard-quickstart-demo-helpdesk to work, it stops after the Human Task step (Review Ticket in this case). The test case passes, so it is not obvious there is a problem, however checking the log output I see that it only logs the 'open ticket' task then exits.

I tracked the change between 0.2.0 and 0.3.0.CR1 that causes the test to stop after the Human Task down to the org.switchyard.component.bpm.task.jbpm.CommandBasedWSHumanTaskHandler.executeTask(Task task, TaskManager taskManager) method, this commented line:

// tasks get completed by humans!

// taskManager.completeTask(task.getId(), task.getResults());

If I uncomment it, the test runs through completely.

Is there an alternative way to get the test to complete besides this?

1. Re: BPM process stops after Human Task in 0.3.0.CR1

kcbabo Nov 28, 2011 8:26 AM (in response to jmorr003)

Thanks for catching this. I believe the idea was that the process would be signaled from the jBPM console instead of being completed automatically by the handler. We should be able to signal the process from the test through the task server to accomplish the same thing, however. David should be able to provide a bit more context on why this changed.
Actions
2. Re: BPM process stops after Human Task in 0.3.0.CR1

kcbabo Nov 28, 2011 7:00 PM (in response to kcbabo)

I chatted with David about this today and it appears to be a test issue only. The test is not communicating with the task server to complete task items. He's going to have a look right after he fixes another blocker issue for our 0.3 release this week.

cheers,
keith
Actions
3. Re: BPM process stops after Human Task in 0.3.0.CR1

jmorr003 Nov 28, 2011 7:14 PM (in response to kcbabo)

That makes sense that it is a test only issue. Thanks.
Actions

Go to original post