activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gnome <chesn...@hotmail.com>
Subject Redelivery header and AMQ broker failure
Date Tue, 21 Jan 2014 10:02:39 GMT
I would like to take advantage of the Redelivery flag to identify potential
message duplicates that going through our system in event of failure.

When consumer failure occurs and the JMS connection is established in
CLIENT_ACKNOWLEDGE mode, redelivery mechanism of inflight messages is
working well and messages are flagged as redelivered.
When the broker fails, inflight messages are redelivered, however the JMS
redelivered header is not set.

I found the old related issue https://issues.apache.org/jira/browse/AMQ-3519
that was resolved with introduction of kaha configuration attribute
rewriteOnRedelivery. Still the redelivered header is not set to true. 
Does rewriteOnRedelivery only applies to transacted connections? Is there
any way to enable this feature without the use of transactions?








--
View this message in context: http://activemq.2283324.n4.nabble.com/Redelivery-header-and-AMQ-broker-failure-tp4676557.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message