-
View this message in context:
http://activemq.2283324.n4.nabble.com/Broker-redelivery-not-working-tp4709185.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Oh well ... got it working now. I did not inject the TransactionManager
into the XaPooledConnectionFactory.
That took a while to figure out.
Christian
On 30.10.2015 23:32, Christian Schneider wrote:
I tested with an external broker now and the message is consumed so it
is not rolled back at al
I tested with an external broker now and the message is consumed so it
is not rolled back at all.
As I am quite sure the XA transaction happens and is rolled back my
assumption is that the ActiveMQXASession does not participate in the
transaction.
I thought the bean org.apache.activemq.jms.pool.
The Bookrepository uses Aries JPA. The class is marked @Transactional.
So it will start an XA transaction before each call or join one.
For the camel route that start with jms: the JMSComponent is injected
with a PlatformTransactionManager. This causes camel to start a
transaction before recei
What is the actual code doing XA? I look at the examples and I
couldn't pinpoint one.
On Fri, Oct 30, 2015 at 3:33 PM, Christian Schneider
wrote:
> I am currently doing a demo for XA transactions that should show how to
> combine JMS and JPA in one transaction.
>
> My code is at:
> https://github
I am currently doing a demo for XA transactions that should show how to
combine JMS and JPA in one transaction.
My code is at:
https://github.com/Talend/tesb-rt-se/tree/ebook-example/examples/tesb/ebook
I am pretty sure my setup for the XA Transactions is correct now. In my
logs I see that JMS
