I'm working on setting up ActiveMQ in a JDBC master/slave topology. It will
also need to participate in XA transactions. When tracing through the code,
I was surprised to see this in the JDBCPersistenceAdapter:
private MemoryTransactionStore transactionStore;
So when using pure JDBC for message persistence, your only options is an
in-memory transaction store? Maybe I'm missing something, but what good is
it to store prepared XA transactions in memory?
If I'm misinterpreting this, how do I go about setting up a persistent
transaction store while using JDBC message persistence? Or more broadly, how
do I configure ActiveMQ so that I can recover any transactions that have
been prepared in the event of failure?
--
View this message in context:
http://www.nabble.com/Only-memory-transaction-store-with-JDBC-persistence-adapter---tp18657395p18657395.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
