Return-Path: X-Original-To: apmail-qpid-users-archive@www.apache.org Delivered-To: apmail-qpid-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 65E1C9C38 for ; Sun, 6 May 2012 10:39:12 +0000 (UTC) Received: (qmail 89141 invoked by uid 500); 6 May 2012 10:39:12 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 89082 invoked by uid 500); 6 May 2012 10:39:11 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 89060 invoked by uid 99); 6 May 2012 10:39:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 May 2012 10:39:11 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of fraser.adams@blueyonder.co.uk designates 81.103.221.49 as permitted sender) Received: from [81.103.221.49] (HELO mtaout03-winn.ispmail.ntl.com) (81.103.221.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 May 2012 10:39:02 +0000 Received: from know-smtpout-1.server.virginmedia.net ([62.254.123.1]) by mtaout03-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20120506103840.IDKB10053.mtaout03-winn.ispmail.ntl.com@know-smtpout-1.server.virginmedia.net> for ; Sun, 6 May 2012 11:38:40 +0100 Received: from [82.33.36.91] (helo=[192.168.1.2]) by know-smtpout-1.server.virginmedia.net with esmtpa (Exim 4.63) (envelope-from ) id 1SQyqJ-0000b3-4U for users@qpid.apache.org; Sun, 06 May 2012 11:37:31 +0100 Message-ID: <4FA65465.9030801@blueyonder.co.uk> Date: Sun, 06 May 2012 11:37:25 +0100 From: Fraser Adams User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: "users@qpid.apache.org" Subject: QMF2 doesn't seem to behave as expected in federated network Content-Type: multipart/alternative; boundary="------------060000080201070508070207" X-Cloudmark-Analysis: v=1.1 cv=JvdXmxIgLJv2/GthKqHpGJEEHukvLcvELVXUanXFreg= c=1 sm=0 a=eFosVe0FMc8A:10 a=m0RCawSgpGEA:10 a=3NElcqgl2aoA:10 a=mV9VRH-2AAAA:8 a=jvu93TJtO4AuAAXMy2oA:9 a=6UEeUT6w-e-M94zEYaoA:7 a=wPNLvfGTeEIA:10 a=2JkUQVG1PbSsCU1_nPMA:9 a=eakZCnUgFLcfu-u81HcA:7 a=_W_S_7VecoQA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 X-Virus-Checked: Checked by ClamAV on apache.org --------------060000080201070508070207 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, I'm looking through a bunch of QMF2 object properties and statistics and things don't seem to add up (all qpid 0.12) I've stood up two brokers and have created a source queue route between them qpid-config add queue federate --limit-policy=ring qpid-config bind amq.match federate fedkey all data-service=amqp-delivery qpid-route -s queue add localhost:5673 localhost:5672 amq.match federate However I cut this, whether I use source routes or standard routes or whether I do qpid-config -a localhost:5673 etc. and fire up the route in the opposite direction the same general thing happens (or rather doesn't!!!!!!). I'd have expected the connection QMF objects describing the inter broker connection to give a little more info.... The federationLink and systemConnection properties remain resolutely "false" when that's definitely not the case and incoming remains "true" whatever I do. Is there any point to these properties? am I doing something wrong? There seems no point in presenting the info from them in my application as the information seems very misleading. Also the remote process name and remote PID property seems to be unset on federated links, it might be nice if it was set to qpidd. Also looking through the QMF2 project page documentation https://cwiki.apache.org/qpid/qmfv2-project-page.html there is a paragraph thus: *Federation is supported.* In QMFv1, messages cannot be transferred over federation links between brokers. Each broker represents its own isolated QMF domain. In QMFv2, agents and consoles can connect to any broker in a federated network and interact with other agents and consoles anywhere in the network. So what this seems to be implying is that should I connect a QMF2 Console to any broker in a federated network I *should* be able to see information for any broker in the network, this doesn't *seem* do be happening. Is this mode of operation actually supported, is there anything that I need to do? getObjects("broker") seems to resolutely only return a single entry. Cheers, Frase --------------060000080201070508070207--