f you could elucidate the ActiveMQ support in duplicate
detection even more, thank you very much. Christian.
--
View this message in context:
http://www.nabble.com/Reconciliation-after-ActiveMQ-server-crash.-tp20734165p20801684.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
So what you are saying is that owing to XA transaction semantics, if the
producer was transactional it could deduce if its message made it to the
broker or not ?
Cool talking to you guys - Christian.
--
View this message in context:
http://www.nabble.com/Reconciliation-after-ActiveMQ-server-cr
th this ambiguity. In
some
cases, this
may cause a client to produce functionally duplicate messages.
A message that is redelivered due to session recovery is not
considered a
duplicate message.
==
--
View this message in context:
http:/
due to session recovery is not
considered a
duplicate message.
==
--
View this message in context:
http://www.nabble.com/Reconciliation-after-ActiveMQ-server-crash.-tp20734165p20734165.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
te message.
==
--
View this message in context:
http://www.nabble.com/Reconciliation-after-ActiveMQ-server-crash.-tp20734165p20734165.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
