Note: the version of the python QMF client where I have seen this is rather old. (0.20) It is even a patched version to make v2 QMF work at all. I must presume that you're using a new enough version (as part of your new enough qpid-too) to have the final version of those patches (see list discussion from about a year ago), so if you can't duplicate it with the modern python qpid-qmf console, and Jakup's problem is elsewhere, I wouldn't be totally surprised.
Bill On Mon, Apr 28, 2014 at 4:11 PM, Jakub Scholz <[email protected]> wrote: > Raised as QPID-5728. > > Thanks & Regards > Jakub > > > On Mon, Apr 28, 2014 at 9:40 PM, Ted Ross <[email protected]> wrote: > > > Please raise a Jira. We can get it fixed. > > > > -Ted > > > > On 04/28/2014 03:12 PM, Jakub Scholz wrote: > > > Hi Ted, > > > > > > Well, it is not critical in terms of actually breaking some > > functionality - > > > it just makes the qpid-tool even less useful than before. Although I > > guess > > > if the problem is in the Python QMF library it self (as mentioned by > > Bill) > > > it can break some custom tools based on these libraries. > > > > > > Should I enter a JIRA for it? Or do you want to keep it as it is? > > > > > > Regards > > > Jakub > > > > > > > > > On Mon, Apr 28, 2014 at 6:54 PM, Ted Ross <[email protected]> wrote: > > > > > >> Jakub, > > >> > > >> The broker object is in fact duplicated/aliased. I don't see (nor do > I > > >> expect) any duplicates in the queue list. > > >> > > >> The aliasing of the broker object is a side-effect of the dual > protocol. > > >> I suppose it could be considered a bug in qpid-tool but I don't think > > >> it's a serious one. > > >> > > >> -Ted > > >> > > >> On 04/26/2014 12:09 PM, Jakub Scholz wrote: > > >>> Hi, > > >>> > > >>> I noticed that when I run my broker (0.28 RC1) with both QMF1 and > QMF2 > > >>> enabled, the qpid-tool shows all of the QMF objects twice. For > example > > >> the > > >>> "list broker" command returns: > > >>> ID Created Destroyed Index > > >>> > > ===================================================================== > > >>> 129 16:03:39 - amqp-broker > > >>> 130 16:03:39 - > org.apache.qpid.broker:broker:amqp-broker > > >>> > > >>> the "list queue" returns: > > >>> ID Created Destroyed Index > > >>> > > >>> > > >> > > > ================================================================================= > > >>> 149 16:03:44 - 173.qmfc-v2-hb-withe.14631.1 > > >>> 150 16:03:44 - 173.qmfc-v2-ui-withe.14631.1 > > >>> 151 16:03:44 - 173.qmfc-v2-withe.14631.1 > > >>> 152 16:03:44 - 173.reply-withe.14631.1 > > >>> 153 16:03:44 - 173.topic-withe.14631.1 > > >>> 154 16:03:44 - > > >>> org.apache.qpid.broker:queue:qmfc-v2-hb-withe.14631.1 > > >>> 155 16:03:44 - > > >>> org.apache.qpid.broker:queue:qmfc-v2-ui-withe.14631.1 > > >>> 156 16:03:44 - > > >>> org.apache.qpid.broker:queue:qmfc-v2-withe.14631.1 > > >>> 157 16:03:44 - > > >>> org.apache.qpid.broker:queue:reply-withe.14631.1 > > >>> 158 16:03:44 - > > >>> org.apache.qpid.broker:queue:topic-withe.14631.1 > > >>> > > >>> Are the QMF1 and QMF2 supposed to be mutually exclusive or is this a > > bug > > >> in > > >>> the qpid-tool? > > >>> > > >>> Regards > > >>> Jakub > > >>> > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: [email protected] > > >> For additional commands, e-mail: [email protected] > > >> > > >> > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
