Bug 494399 – Bindings from durable queues to the default exchange are not shown after restore

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 494399 - Bindings from durable queues to the default exchange are not shown after restore

Summary:	Bindings from durable queues to the default exchange are not shown after restore

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	qpid-qmf (Show other bugs)
Sub Component:
Version:	1.1.1
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	1.3
Target Release:	---
Assigned To:	Ted Ross
QA Contact:	Jan Sarenik
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	501015
Blocks:
	Show dependency tree / graph

Reported:	2009-04-06 13:28 EDT by Ted Ross
Modified:	2011-08-12 12:03 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Bindings from a durable queue to the default exchange (named "") was not visible through management after a broker restart and restore. This did not affect the proper message forwarding of the broker. With this update, bindings from durable queues to the default exchange are visible as expected.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-10-14 12:15:20 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2010:0773	normal	SHIPPED_LIVE	Moderate: Red Hat Enterprise MRG Messaging and Grid Version 1.3	2010-10-14 11:56:44 EDT

Groups: None (edit)

Description Ted Ross 2009-04-06 13:28:21 EDT

Description of problem:

The binding from a durable queue to the default exchange (named "") is not visible via management after a broker restart and restore.  This does NOT affect the proper message forwarding of the broker.

Version-Release number of selected component (if applicable):

1.1.1

How reproducible:

100%

Steps to Reproduce:
1. Create a durable queue (qpid-config add queue D --durable)
2. View the bindings (qpid-config queues -b), see binding from 'D' to ''
3. Restart the broker and re-view the bindings

Comment 2 Ted Ross 2010-01-15 11:26:54 EST

Added dependency on BZ501015.  This will be fixed by the solution to that issue.

-Ted

Comment 3 jrd 2010-02-10 10:36:37 EST

This is fixed as of current trunk.  Could probably close, or wait until we're sure we're done wiht 501015.

Comment 4 Jan Sarenik 2010-03-29 09:32:13 EDT

Easily reproducible on qpid-cpp-server-0.7.916826-2.el5 with cluster and
store by following the described reproduction steps.

Comment 5 Ted Ross 2010-04-23 17:28:26 EDT

This is now fixed in the following upstream revisions:

   Apache Qpid:  937526
   rhmessaging:    3927

Comment 6 Jan Sarenik 2010-05-26 08:37:38 EDT

Verified on RHEL5.5 x86_64,
  qpid-cpp-server-store-0.7.946106-1.el5
  qpid-tools-0.7.946106-4.el5

Comment 7 Jan Sarenik 2010-05-26 08:43:53 EDT

Verified on RHEL4.8 x86_64,
  qpid-cpp-server-store-0.7.946106-1.el4
  qpid-tools-0.7.946106-4.el4

Comment 8 Jan Sarenik 2010-05-26 08:50:59 EDT

Verified also on the same package builds for RHEL5.5 and RHEL4.8 on i386.

Comment 9 Martin Prpič 2010-10-07 09:21:14 EDT

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Bindings from a durable queue to the default exchange (named "") was not visible through management after a broker restart and restore. This did not affect the proper message forwarding of the broker. With this update, bindings from durable queues to the default exchange are visible as expected.

Comment 11 errata-xmlrpc 2010-10-14 12:15:20 EDT

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0773.html

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