Bug 700107 - Durable messages redelivered flag
Summary: Durable messages redelivered flag
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Programming_Reference
Version: 2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: 2.2
: ---
Assignee: Joshua Wulf
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-27 13:43 UTC by ppecka
Modified: 2014-10-19 22:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-20 03:13:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description ppecka 2011-04-27 13:43:19 UTC
Description of problem:
As AMQP documnetation is not defining what state redelivered durable message should be after it's recovered from store. I'm asking for it to be documented in MRG documentation.

Quoting from from:
https://bugzilla.redhat.com/show_bug.cgi?id=640618#c11


===snip===
The broker marks all durable messages as redelivered on restart. This
is because it does not durably record delivery attempts. The setting of the
redelivered flag is a hint, not a guarantee. It is usually better to suggest
that the application check whether it has seen a message that may never have
been redelivered rather than fail to hint about a message that has been
redelivered.
===cut===

Comment 1 Gordon Sim 2011-04-27 16:35:01 UTC
Perhaps add a footnote to table 2.9 in Programming with Apache Qpid?

Comment 2 Joshua Wulf 2012-05-09 14:29:34 UTC
Red_Hat_Enterprise_MRG-Messaging_Installation_and_Configuration_Guide-2.2-web-en-US-0-4.el6eng.src.rpm

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2.2/html-single/Messaging_Installation_and_Configuration_Guide/index.html#Durable_Message_State_After_Restart

Comment 4 Cheryn Tan 2012-09-20 02:54:21 UTC
Released for MRG 2.2


Note You need to log in before you can comment on or make changes to this bug.