Error custom task operation

Question

Hi
Sometimes i get an error in the bpel server control when i am performing a custom task operation ' wlSvc.customTaskOperation(ctx, pTask.getTaskId(), actionDONE);'
the error is: <2005-12-05 17:22:45,421> <ERROR> <default.collaxa.cube.engine.delivery> <DeliveryService::handleCallback> Activity for conversat
ion MD5{2fde76181d5fe21d621a43444cc2e4d3} has been closed ... marking message d91cbb6d4f175ff0:6fa9fc:107fcbcea7e:-7f50 as cancelled.
But i can't understand what is happeening because it doesn't happens all the time
Here is my source code
public void completeTask(IWorklistTask pTask,String asignee,String password,String action)throws Exception{
WorklistService wlSvc =WorklistService.getWorklistService();
IWorklistContext ctx = wlSvc.authenticateUser(user, asigneePassword);
wlSvc.updateTask(ctx,pTask);
String actionDONE = action;
wlSvc.customTaskOperation(ctx, pTask.getTaskId(), actionDONE);
thanks Nicolas Fonnegra M

Answer 1

Solved !!!!!!!!!!!!!!!!
The TaskActionHandler was cancelling the message delivered by the 'customTaskOperation'. Normally, for the source code I posted before, the TaskActionHandler receives two messages, one from the updateTask and another from the 'customTaskOperation'. It seems that sometimes the 'customTaskOperation' messages arrive while the TaskActionHandler is still processing the updateTask messages, so the TaskActionHandler simply cancells the newly arrived ones. That is why in the worklist application you have two different actions , one for updating the info and one for completing the task, so the system avoid 'customTaskOperation' messages that arrive 'too early'.
I simply put a delay between the two operations and it worked fine.
wlSvc.updateTask(ctx,pTask);
String actionDONE = action;
Thread.sleep(3000); // I haven't tried with less time,but with 3 seconds works great
wlSvc.customTaskOperation(ctx, pTask.getTaskId(), actionDONE);
thanks Nicolas Fonnegra M.