topic Re: Activiti listener db updates - are they atomic ? in Alfresco Archive

Activiti listener db updates - are they atomic ?

davanna — Thu, 16 Jun 2016 17:44:13 GMT

Hi Members,I have written event listeners for events - PROCESS_STARTED and TASK_CREATED. In the event listener I am calling my custom db inserts (these are not activiti tables) for PROCESS_STARTED and TASK_CREATED. For PROCESS_STARTED, it inserts record into 'workflow' table and for TASK_CREATED, it

Re: Activiti listener db updates - are they atomic ?

davanna — Fri, 17 Jun 2016 03:37:59 GMT

I was able to get to understand the problem. I am using Spring boot and I have defined the JPATransactionManager for my database and it is being used by Activiti. Hence if there is any exception in event listener calling my code, the db rollbacks for my table are done. I have defined the bean for datasource defining the Activiti database as primary. But I am not sure how Activiti is using the TransactionManager of my database and working properly. The Spring documentation clearly mentions that if no transaction manager is created, it will create a default transactionmanager. But if any transaction manager is created, it will use it. Using the transaction manager of my database, Activiti is working fine. I am trying to understand this piece here. We are deploying to production and wanted to make sure I understand it properly. Can anybody shed some light here ?

Re: Activiti listener db updates - are they atomic ?

jbarrez — Wed, 22 Jun 2016 09:17:24 GMT

You inject the transaction manager into the Activiti process engine configuration. Activiti and the custom database calls will be done in the same transaction in that case (if they are the same datasource, with multiple you need XA datasources).