topic DataSourceTransactionManager or JTATransactionManager in Alfresco Archive

DataSourceTransactionManager or JTATransactionManager

rangoo — Sat, 08 Feb 2014 07:29:24 GMT

I have 3 applications using same activiti datasource. Each App doing different things though1st App - Reads JMS and triggers workflows2nd App - Continues Async WorkFlows3rd App - REST APII am currently using datasourcetransactionmanager.<bean id="transactionManager" class="org.springframework.jdb

Re: DataSourceTransactionManager or JTATransactionManager

frederikherema1 — Mon, 10 Feb 2014 08:56:43 GMT

If you're using spring, we wrap the datasource in a TransactionAwareDatasourceProxy (if not already of that instance) to make sure Activiti used the same transaction. If you use the same transactionManager instance for all of your apps (see platformTransactionManger property on SpringProcessEngineCOnfiguration), this will work without a problem, using only ONE transaction. This only works, of course, if you're in the same spring-context.

Not really sure if your apps reference each other - eg. a transactional service is called from within the execution of a service-task. If so, and the Datasource is the same JTA won't be more usefull as just using the same "PlatformTransactionManager", as no datasources need to be synchronised. If the apps do NOT reference each other, there is no need for a single transactiobn-manager, as the transactions will never be mixed work from multiple apps.

Re: DataSourceTransactionManager or JTATransactionManager

rangoo — Mon, 10 Feb 2014 18:32:29 GMT

Just to clarify - All 3 apps are independent use their own spring-context so they use 3 TransactionManagers (all of type datasourcetransactionmanager) pointing to same Activiti Datasource(with Global Transaction being disabled & one phase commit enabled). Do you still think there will be no issues using datasourcetransactionmanager?

Re: DataSourceTransactionManager or JTATransactionManager

trademak — Tue, 11 Feb 2014 15:16:14 GMT

Each app will perform its action against Activiti in its own transaction. So don't think there will be an issue with this approach technically. You only need to be aware that each app will perform its logic against Activiti in a separate transaction. Also when multiple apps access the same process instance at the same time, only one will win and the other one will get an exception.

Best regards,

Re: DataSourceTransactionManager or JTATransactionManager

rangoo — Tue, 11 Feb 2014 16:33:38 GMT

Thanks both of you guys.