Hi Bill, I've just tried to restrict my broker to using only qmf v2:
$ qpidd --auth no --mgmt-qmf1 no and I no longer get update notifications from my console.py app! From the looks of it, the console.py code is broken - the broker is generating the qmfv2 updates, but console.py is dropping them. This is on trunk - I'll open a JIRA. Other notes: 1) re: qpidtoollib - doesn't sound like this would work for you since you need async object update notifications. Currently qpidtoollibs only support query/response and event monitoring. We probably should add async object updates, too, but right now that's not there. 2) uniquely identifying objects across multiple brokers. Yes, Gordon's correct, object names are usually only guaranteed to be unique within a broker, not across them. Partitioning them by IP address + port could work, as would the federation tag from the vhost object. ----- Original Message ----- > From: "Bill Freeman" <ke1g...@gmail.com> > To: users@qpid.apache.org > Sent: Monday, April 1, 2013 1:35:54 PM > Subject: Re: Questions from a novice > > On Mon, Apr 1, 2013 at 12:21 PM, Gordon Sim <g...@redhat.com> wrote: > > > On 04/01/2013 05:06 PM, Bill Freeman wrote: > > > >> since I have a dog and pony show coming up shortly, do you > >> know how to get the existing qmf.console stuff to send my updates as V2 > >> (session has rcvObjects True). > >> > > > > One option might be to turn v1 off at the broker... --mgmt-qmf1=false to > > qpidd. I don't know hoe effective that will be, just a suggestion. > > > > Thanks. I may test with that, but for production I can't be sure that > some department that I don't know about is using a V1 only tool. > -- -K --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
