In a JDBC Master/Slave topology with durable queues if the master fails does the slave pick up the transactions of the master? In other works, if a consumer opens a session against the master, consumes a message, but doesn't commit the transaction and the master dies, does the slave (who is now the new master) know about the transaction? What happens when the client attempts to commit the transaction? Is an error thrown or does the new master handle it properly, i.e., removes the message permanently from the queue?
Rob -- View this message in context: http://www.nabble.com/Transaction-State-tp16968998s2354p16968998.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
