Sending a message to cancel a usertask within same process

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

jkuehn

Hi,

we have a process with two usertasks spawning after a parallel gateway. As long as usertask 1 is not completed, the user should be able to complete usertask 2. Once usertask 1 is completed, usertask 2 should be removed.

How would you model this? Our current approach:

[img]http://picture.ms/images/2013/10/08/parallelUserMessagebTPsf.png[/img]

We try to solve it using a message. The problems we are having:
* Sending a message to usertask 2 with execution.getEngineServices().getRuntimeService().messageEventReceived(MESSAGE_NAME, executionIdOfUsertask2); from servicetask successfully ends usertask 2, calls "Do some stuff" and goes to the end event. But: the process will not be finished, "Send Message to Cancel Usertask " servicetask remains active.
* Sending a message to usertask 2 with execution.getEngineServices().getRuntimeService().messageEventReceived(MESSAGE_NAME, executionIdOfUsertask2); from servicetask in a seperate thread successfully cancels usertask 2 and finishes the process the desired way, but throws ActivitiOptimisticLockingException occasionally.

Catching ActivitiOptimisticLockingException didn't work. I tried to implement a retry loop as has been suggested in another discussion, but the catch clause doesn't catch ActivitiOptimisticLockingException:

int retries = 3;
while (retries > 0) {
    try {
        runtimeService.messageEventReceived(messageName, task.getExecutionId());
        break;
    } catch (ActivitiOptimisticLockingException ex) {
        if (–retries < 1) {
            // fatal, escalate
        }

        try {
            // give some time to recover, allow other instance to finish work on process
            Thread.sleep(100);
        } catch (InterruptedException e) {}
    }
}
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Do you have some hints?

Thanks, greetings, Juri

jkuehn

Small update:

ActivitiOptimisticLockingException is caught correctly, i was logging to std out and misinterpreted the output.

The ActivitiOptimisticLockingException occurs after recieving the message and executing "Do some stuff" service task. After the exception, the usertask 2 remains active. On a retry to send the message again, no exception occurrs and the process ends as desired. But the "Do some stuff" servicetask has been executed 2 times in that case.

Gateway->usertask1->servicetask send message->endevent
message event->servicetask do some stuff->endevent –> ActivitiOptimisticLockingException triggers retry –>message event->servicetask do some stuff->endevent

Can i implement some sort of queue, to avoid concurrent modifications? How to check whether a process is locked? Is there a better way to model this use case?