k, at least you have a workaround. I had a peek at the code and I see what you saw.. this is a regression from https://issues.apache.org/jira/browse/AMQ-4019 the xa factory has been left behind a bit with that refactor. On 7 November 2012 12:21, jsimmonsc wrote: > My entire context is below. > > If I switch out the org.apache.activemq.pool.XaPooledConnectionFactory with > a org.fusesource.jms.pool.XaPooledConnectionFactory, everything works as > expected except for the previously mentioned memory leak fixed in AMQ-3997. > > > Just in case it's needed, my route: > > from("activemq:josh.test.queue") > .transacted() > .to("activemq:josh.test.queue2") > .process(new Processor() { > public void process(Exchange arg0) throws Exception { > Thread.sleep(5000); > } > }) > .rollback(); > My context: > > > > josh.test > > > location="file:${user.home}/ApplicationData/amq.properties" /> > > interface="org.springframework.transaction.PlatformTransactionManager"/> > interface="javax.transaction.TransactionManager"/> > > class="org.apache.camel.spring.spi.SpringTransactionPolicy"> > ref="osgiPlatformTransactionManager"/> > value="PROPAGATION_REQUIRED"/> > > > class="org.apache.activemq.ActiveMQXAConnectionFactory"> > > > > > > class="org.apache.activemq.pool.XaPooledConnectionFactory" > init-method="start" destroy-method="stop"> > > /> > /> > > > class="org.apache.camel.component.jms.JmsConfiguration"> > > ref="osgiPlatformTransactionManager"/> > > > > class="org.apache.activemq.camel.component.ActiveMQComponent"> > > > > > > > -- > View this message in context: http://activemq.2283324.n4.nabble.com/XaPooledConnectionFactory-tp4658865p4658913.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com