DataSourceTransactionManager or JTATransactionManager

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.

rangoo

I have 3 applications using same activiti datasource. Each App doing different things though

1st App - Reads JMS and triggers workflows
2nd App - Continues Async WorkFlows
3rd App - REST API

I am currently using datasourcetransactionmanager.

<bean id="transactionManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
    <property name="dataSource" ref="dataSource" />
  </bean>
 
  <bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration">
    <property name="dataSource" ref="dataSource" />
    <property name="transactionManager" ref="transactionManager" />
    <property name="databaseSchemaUpdate" value="true" />
    <property name="jobExecutorActivate" value="false" />
  </bean>

I guess in this case Spring creates 3 transaction Managers but the Connection pool is the same.  Wondering If I should use jtaTransactionManager and leave it to the App server so that single transaction manager takes care of all transactions. Suggestions?

frederikherema1

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.