You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ganesh Murthy (JIRA)" <ji...@apache.org> on 2016/06/28 13:27:57 UTC
[jira] [Comment Edited] (DISPATCH-285) qdmanage returns an empty
list when you QUERY for certain entities
[ https://issues.apache.org/jira/browse/DISPATCH-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15248111#comment-15248111 ]
Ganesh Murthy edited comment on DISPATCH-285 at 6/28/16 1:27 PM:
-----------------------------------------------------------------
We have the concept of short types (for convenience) which when used in qdmanage get expanded to their corresponding long types
For example,
{noformat}
qdmanage QUERY --type=listener
{noformat}
is the same as
{noformat}
qdmanage QUERY --type=org.apache.qpid.dispatch.listener
{noformat}
Here is a mapping of short types to long tyes
||short type||long type||
|listener|org.apache.qpid.dispatch.listener|
|connector|org.apache.qpid.dispatch.connector|
|link|org.apache.qpid.dispatch.router.link|
|node|org.apache.qpid.dispatch.router.node|
|linkRoute|org.apache.qpid.dispatch.router.config.linkRoute|
|address|org.apache.qpid.dispatch.router.config.address|
|autoLink|org.apache.qpid.dispatch.router.config.autoLink|
|??|org.apache.qpid.dispatch.router.address|
Note that in the case of org.apache.qpid.dispatch.router.address, there is no corresponding short type because the shortype _address_ is already taken by _org.apache.qpid.dispatch.router.config.address_
You will have to use the long type of org.apache.qpid.dispatch.router.address to see router addresses.
was (Author: ganeshmurthy):
We have the concept of short types (for convenience) which when used in qdmanage get expanded to their corresponding long types
For example,
{noformat}
qdmanage QUERY --type=listener
{noformat}
is the same as
{noformat}
qdmanage QUERY --type=org.apache.qpid.dispatch.listener
{noformat}
Here is a mapping of short types to long tyes
||short type||long type||
|listener|org.apache.qpid.dispatch.listener|
|connector|org.apache.qpid.dispatch.connector|
|link|org.apache.qpid.dispatch.router.link|
|node|org.apache.qpid.dispatch.router.node|
|linkRoute|org.apache.qpid.dispatch.router.config.address|
|address|org.apache.qpid.dispatch.router.config.address|
|autoLink|org.apache.qpid.dispatch.router.config.autoLink|
|??|org.apache.qpid.dispatch.router.address|
Note that in the case of org.apache.qpid.dispatch.router.address, there is no corresponding short type because the shortype _address_ is already taken by _org.apache.qpid.dispatch.router.config.address_
You will have to use the long type of org.apache.qpid.dispatch.router.address to see router addresses.
> qdmanage returns an empty list when you QUERY for certain entities
> ------------------------------------------------------------------
>
> Key: DISPATCH-285
> URL: https://issues.apache.org/jira/browse/DISPATCH-285
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Management Agent
> Affects Versions: 0.6.0
> Reporter: Ernest Allen
> Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
>
> Start 2 router network in tests/config-2
> qdmanage QUERY -b 0.0.0.0:20100 --type router.link
> The response is an empty list.
> However, if you use qdstat:
> qdstat -b 0.0.0.0:20100 -l
> you get the full list
> You get an empty list from qdmanage for other entities as well.
> router.address
> router.config.address
> and maybe more
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org