Thanks. I'm snowed under. I'll try the patch in a day or so.
Bill On Wed, Apr 3, 2013 at 12:56 PM, Ken Giusti <kgiu...@redhat.com> wrote: > > > ----- Original Message ----- > > From: "Bill Freeman" <ke1g...@gmail.com> > > To: users@qpid.apache.org > > Sent: Wednesday, April 3, 2013 9:45:49 AM > > Subject: Re: Questions from a novice > > > > On Tue, Apr 2, 2013 at 5:22 PM, Ken Giusti <kgiu...@redhat.com> wrote: > > > > > When console.py connects to a broker (via addBroker), it will attempt > to > > > query for the existence of the qmf.default.direct and qmf.default.topic > > > exchanges. If that query succeeds, the console marks that broker as > being > > > V2 capable, and uses V2. Otherwise it falls back to V1. > > > > > > Take a look at the Broker::_tryToConnect() method in console.py for all > > > the gory details. > > > > > > > > And, in fact, my broker has those exchanges, and console.py finds them > and > > sets the Broker instance's brokerSupportsV2 attribute to True. And the > > brokerAgent it gets has isV2 True. And it creates its v2 queues, > > binds/subscribes them, etc. > > > > So I'm guessing that the rcvOjbects flag to the Session constructor only > > gets me V1 updates, and I would have to subscribe explicitly to the > queues > > that I care about in order to get v2 updates. Does that sound right? > > No - you _should_ be getting V2 updates. But your not because of the > aforementioned bug: > > https://issues.apache.org/jira/browse/QPID-4689 > > If you apply the patch given in that above JIRA to your copy of > console.py, you should start receiving V2 object updates. > > I've also found a problem with heartbeats - until I fix that you'll not > get V2 heartbeat indications. > > > In summary, once I fix that bug you should be getting async QMF v2 style > updates. > > > > > > > Bill > > > > -- > -K > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > >
