[rules-users] Weird human task behaviour

I have this strange problem, when I call int taskId = 105; // dummy taskId, the real one is obtained through TaskSummary BlockingTaskOperationResponseHandler b = new BlockingTaskOperationResponseHandler(); client.complete(taskId, "myusername", null, b); while (!b.isDone()){ b.waitTillDone(100); } System.out.println("Completed task "+taskId+" owned by user myusername."); I get this in the log: INFO [STDOUT] Completed task 105 owned by user myusername. INFO [STDOUT] Notification of completed task 104 ...and about 50 milliseconds later... INFO [STDOUT] Notification of aborted task 104 No error messages between these two notifications. I understand that these ID's are not the same because 104 is actually workItemId that holds taskId 105. The status of task 105 in the database table "task" is "Completed", but the workflow stops after it and I can't do anything about it. Is there any known issues with task persistence in JBoss 5.1 or something? -- View this message in context: http://drools.46999.n3.nabble.com/Weird-human-task-behaviour-tp3368608p33... Sent from the Drools: User forum mailing list archive at Nabble.com.