activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: AMQ 4.0 with Oracle Persistence and XA Transactions
Date Tue, 04 Jul 2006 09:43:32 GMT
Which version of ActiveMQ are you using? IIRC there were some
auto-commit bugs fixed in 4.0.1

On 7/4/06, Pep <pep_codina@yahoo.es> wrote:
>
> Hi,
>
> we have ActiveMq acting as our JMS provider for OC4J 10.1.3. It is running
> as embbeded and integrated to OC4J by means of the JCA connector. As it is
> an additional resource provider, I assume our transactions in OC4J should be
> XA.
>
> Also, we had an Oracle persistence in AMQ configured the following way:
>
>     <persistenceAdapter>
>       <journaledJDBC journalLogFiles="5" dataDirectory="../activemq-data"
> dataSource="#oracle-ds"/>
>     </persistenceAdapter>
>
> <bean id="oracle-ds" class="org.apache.commons.dbcp.BasicDataSource"
> destroy-method="close">
>     <property name="driverClassName" value="oracle.jdbc.OracleDriver"/>
>     <property name="url" value="jdbc:oracle:thin:@10.0.0.178:1521:systao"/>
>     <property name="username" value="pep_anthema"/>
>     <property name="password" value="pep_anthema"/>
>     <property name="poolPreparedStatements" value="true"/>
>   </bean>
>
> With this configuration we experienced some deadlocks in the application
> server. My thought was that the persistence in Oracle was running in a
> different transaction. Really, I don't understand where the problem was as
> when using the default derby persistence there is no problem at all.
>
> Then I tried to use the same datasource the application is using. For that
> purpose, I replaced the oracle-ds definition to the following one:
>
>   <bean id="oracle-ds"
> class="org.springframework.jndi.JndiObjectFactoryBean">
>         <property name="jndiName" value="jdbc/xasystao" />
>   </bean>
>
> But with this configuration I am getting these error messages when
> publishing a message to our Queues in AMQ.
>
> 2006-07-04 10:52:40.045 WARNING J2EE DS262 The method 'setAutoCommit(true)'
> cant be called when a global transaction is active.
> 2006-07-04 10:52:40.045 WARNING J2EE DS262 The method 'commit' cant be
> called when a global transaction is active.
>
>
> Any idea?
>
> Thnks!
> --
> View this message in context: http://www.nabble.com/AMQ-4.0-with-Oracle-Persistence-and-XA-Transactions-tf1888956.html#a5164616
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>


-- 

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message