topic Re: Skipping an async ServiceTask with the ManagementService in Alfresco Archive

Skipping an async ServiceTask with the ManagementService

damokles — Mon, 07 Jul 2014 13:18:12 GMT

In our JavaServiceTask we are calling an external REST-Service that is unfortunately not idempotent. Due to an exception the Activiti execution was rolled back after the service call was made. In the subsequent retries the REST call fails since it already knows the transaction id. We need a way to s

Re: Skipping an async ServiceTask with the ManagementService

jbarrez — Mon, 07 Jul 2014 13:28:27 GMT

No, the job won't be deleted in this case. It simply moves the execution pointer further, but leaves the job as-is.
If you need it, you really would have to delete the job in the same command.

However, can't you solve it more gracefully with a try - catch in the async service task? And then in the catch to the appropiate routing?

Re: Skipping an async ServiceTask with the ManagementService

damokles — Mon, 07 Jul 2014 15:33:59 GMT

The problem is that the return code of the REST-Service is not descriptive enough to use a try catch for this scenario, since there might be other errors that have the same status code that should be retried. No ideal I know, but that is how it is at the moment.

EDIT:
Deleting the job would not be the problem. Is there anything else I should be aware of?

Regarding the new ProcessInstanceId, that was an unfortunate error in our monitoring tool which switched executionId and processInstanceId.

Re: Skipping an async ServiceTask with the ManagementService

jbarrez — Wed, 09 Jul 2014 15:58:54 GMT

No, if you do a delete of the job, and execute a default bpmn 2.0 leave with the execution - should mimic what the job would normally do.