topic Re: ActivitiException causing rollback inspite of catching it in Alfresco Archive

ActivitiException causing rollback inspite of catching it

hepci123 — Wed, 16 Jul 2014 18:29:57 GMT

Hi,We are using Spring+Activiti+JTA in our application. The method that calls RuntimeService.startProcessInstanceByKey has a try catch for ActivitiException as we do not want the transaction to be rolled back when the exception occurs. But everytime ActivitException occurs I see that the transaction

Re: ActivitiException causing rollback inspite of catching it

trademak — Mon, 21 Jul 2014 10:11:18 GMT

Why is your process instance throwing an ActivitiException? Is it happening in a service task? Then you could catch the Exception there. You can also use asynchronous activities to commit the transaction after the process instance is started.

Best regards,

Re: ActivitiException causing rollback inspite of catching it

hepci123 — Tue, 22 Jul 2014 20:39:28 GMT

Hi,

Thank you for your response.

A gateway in one of our workflows was missing default flow so everytime the gateway conditions are not met, activiti is throwing below exception

org.activiti.engine.ActivitiException: No outgoing sequence flow of the exclusive gateway 'actionBlockGateway' could be selected for continuing the process

Even though poorly constructed workflow caused this exception in the above scenario, we still need to handle such scenarios as our customers are creating these and may not be as familiar with activiti.

Our workflow tasks need to be executed sequentially so I don't think using async tasks suits our implementation. We have disabled JTA on the queue for now as we had a release. We'll soon need to figure out how to stop this loop due to Spring rollback on ActivitiException and release a patch. Any help in this regard is great!

Thanks!

Re: ActivitiException causing rollback inspite of catching it

jbarrez — Fri, 25 Jul 2014 07:56:48 GMT

If your transaction management is configured correctly, this should work. I suspect a misconfiguration.

How does your transaction config look like (Spring-side and Actviiti-side) ?

An alternative is to add your own command (copied from the regular start process instance command, but now with an exception catch), execute it through managementService.executeCommand.().