Thank you Jirik and Ganesh, I will use a workaround from my side while waiting for the official release of 0.7.0 and fixes of the jira issues mentioned.
Regards, Adel > From: [email protected] > Date: Fri, 1 Jul 2016 17:35:31 +0200 > Subject: Re: [Qpid-Dispatch] qdmanage query doesn't take into account the > name option when passed > To: [email protected] > > Hello Adel, > > On Fri, Jul 1, 2016 at 5:23 PM, Adel Boutros <[email protected]> wrote: > > > I have one more question: What is considered a "Management entity"? > > > > I have a feeling the "READ" only works with the "connector" type because > > with the other types, I am getting some weird exceptions: > > > > bash$ qdmanage -b amqp://localhost:10452 read --type=connector > > BadRequestStatus: No name or identity provided > > > > This is as it should be. Read takes either --name or --identity. Query > takes --type. > > > > bash$ qdmanage -b amqp://localhost:10452 read --type=address > > Timeout: Connection amqp://localhost:10452/$management timed out: Waiting > > for response > > > > This is a bug, I encountered it too. It is fixed in the current git tip. > > > > bash$ qdmanage -b amqp://localhost:10452 read --type=autoLinks > > BadRequestStatus: No such entity type 'org.apache.qpid.dispatch.autoLinks' > > > > First, you are not supposed to use --type with read, second, the type is > autoLink, not autoLinks. When you use version with the Timeout bug fixed, > you would see "BadRequestStatus: No name or identity provided". Use > `qdmanage query`. > > In case you missed it, I reported some issues about qdmanage > * https://issues.apache.org/jira/browse/DISPATCH-411 > * https://issues.apache.org/jira/browse/DISPATCH-408 > * https://issues.apache.org/jira/browse/DISPATCH-409 > > you may encounter those too.
