Atomikos Forum

Hi,

I'm currently integrating Transaction Essentials into a Tomcat 7 server.

My configuration in context.xml is as follows:
  ‘<Transaction factory="com.atomikos.icatch.jta.UserTransactionFactory" />

  <Resource name="jdbc/OracleNarDs" auth="Container"
            type="com.atomikos.jdbc.AtomikosDataSourceBean"
            factory="com.atomikos.tomcat.EnhancedTomcatAtomikosBeanFactory"
            uniqueResourceName="jdbc/OracleNarDs"
            xaDataSourceClassName="oracle.jdbc.xa.client.OracleXADataSource"
            xaProperties.user="dries_nar"
            xaProperties.password="dries_nar"
            xaProperties.URL="jdbc:oracle:thin:@10.0.52.135:1521:fed"
            maxPoolSize="20"
            minPoolSize="10"
            testQuery="SELECT 1 FROM DUAL"/>

I've added the lifecycle listener defined on the wiki and I'm integrating Atomikos with hibernate by adding the TransactionManagerLookup. Since I'm using JPA I don't need the factory.

In my Spring xml file I've used:
<tx:jta-transaction-manager/>

This oonfiguration works, but has the disadvantage that transaction  suspension is impossible. I was wondering if it is possible to expose the TransactionManager itself to JNDI, so that it can be used from Spring.

Any ideas on how this issue can be resolved?

Kind regards,

Dries

Hi,

JNDI exposure of Atomikos in Tomcat is provided out-of-the-box in our commercial subscription... It also includes the right startup/shutdown wrt resource connectors to ensure recovery is correct.

Cheers