Bug 572221 - Binding to <unknown> reported by qpid-config in persistent cluster.
Summary: Binding to <unknown> reported by qpid-config in persistent cluster.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: Development
Hardware: All
OS: Linux
high
high
Target Milestone: 1.3
: ---
Assignee: Ted Ross
QA Contact: Jeff Needle
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-10 15:24 UTC by Alan Conway
Modified: 2010-10-20 13:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-20 11:30:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alan Conway 2010-03-10 15:24:50 UTC
Description of problem:

Following the instructions to reproduce bug 557243 qpid-config reports a strange binding:

Exchange '' (direct)
    bind [falcons] => <unknown>

Where it should be bound to the queue "falcons" The broker appears to route messages correctly however. 

How reproducible: easy

Steps to Reproduce: bug 557243 comment 0

Comment 1 Alan Conway 2010-03-25 19:04:00 UTC
On the first broker, qpid-config is getting a queue objectId of 0-0-0-0-0 which gives rise to the <unknown> display. Adding some trace statements to the broker shows that the object ID for the falcons queue is different (one higher) on the first broker than on the other two, but it is set to a non-0 value in setPersistenceId.

Comment 2 Alan Conway 2010-03-25 19:22:17 UTC
This bug also affects standalone brokers, a simpler way to reproduce it:

MSGSTORE_MODULE=<path-to-msgstore.so>
qpidd -d --auth=no --load-module=$MSGSTORE_MODULE
qpid-config add queue falcons --durable
qpidd -q
qpidd -d --auth=no --load-module=$MSGSTORE_MODULE
qpid-config -b exchanges

The output inclues:

Exchange '' (direct)
    bind [falcons] => <unknown>

Comment 3 Ted Ross 2010-04-26 19:12:30 UTC
This is fixed upstream:
  Apache Qpid:  revision 937526
  Rhmessaging:  revision 3927

Comment 4 Jiri Kolar 2010-05-31 11:39:12 UTC
Tested:
on 752581 bug appears
on 946106 does not. It has been fixed

validated on RHEL 5.5 and RHEL4 i386 / x86_64

packages:

# rpm -qa | grep -E '(qpid|openais|rhm)' | sort -u

openais-0.80.6-16.el5_5.1
openais-debuginfo-0.80.6-16.el5_5.1
python-qpid-0.7.946106-1.el5
qpid-cpp-client-0.7.946106-1.el5
qpid-cpp-client-devel-0.7.946106-1.el5
qpid-cpp-client-devel-docs-0.7.946106-1.el5
qpid-cpp-client-ssl-0.7.946106-1.el5
qpid-cpp-mrg-debuginfo-0.7.935473-1.el5
qpid-cpp-server-0.7.946106-1.el5
qpid-cpp-server-cluster-0.7.946106-1.el5
qpid-cpp-server-devel-0.7.946106-1.el5
qpid-cpp-server-ssl-0.7.946106-1.el5
qpid-cpp-server-store-0.7.946106-1.el5
qpid-cpp-server-xml-0.7.946106-1.el5
qpid-java-client-0.7.946106-3.el5
qpid-java-common-0.7.946106-3.el5
qpid-tools-0.7.946106-4.el5
rhm-docs-0.7.946106-1.el5

->VERIFIED


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