Thanks for your reply!
So one could argue that the once-and-only-once guarantee of the jms spec
cannot be fulfilled in the special edge case, where there's a not yet
committed, reply lost happening.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Transactional-Message
();
}
}
}
Thanks for your help!
Michael
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Transactional-Message-Lost-On-Failover-tp4692426.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
();
} catch (JMSException e) {
e.printStackTrace();
}
}
}
Thanks for your help!
Michael
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Transactional-Message-Lost-On-Failover-tp4692426.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
