Forgot to mention the test was run on ActiveMQ v4.1.1
--
View this message in context:
http://www.nabble.com/Transaction-State-tp16968998s2354p17028108.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
1:1:2],
value=prop_value_2:1209756576693
[consumer-1] Fri May 02 14:31:49 CDT 2008: Committing transaction...
--
View this message in context:
http://www.nabble.com/Transaction-State-tp16968998s2354p17026701.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ts the transaction?
--
View this message in context:
http://www.nabble.com/Transaction-State-tp16968998s2354p16986567.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
this message in context:
http://www.nabble.com/Transaction-State-tp16968998s2354p16968998.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Transactional state is replayed from the client - so the new master
will remove the message from the store
cheers,
Rob
s 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/Transa