Can someone point me to where the the behavior of the JDBC Master/Slave topology is explained, specifically with respect to how transactions are managed during failover?
I thought that uncommitted transactions would seamlessly failover to the slave but I'm seeing behavior that suggests this is not the case and I can't find any documentation that explains how this should work. A pointer would be much appreciated. Thanks, Rob -- View this message in context: http://www.nabble.com/JDBC-Master-Slave-Failover-Behavior-tp17063521s2354p17063521.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
