You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Paolo Patierno (JIRA)" <ji...@apache.org> on 2016/06/09 07:57:20 UTC

[jira] [Updated] (DISPATCH-374) qdmanage: using --type option with --name (or --identity) option causes a "Not found"

     [ https://issues.apache.org/jira/browse/DISPATCH-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paolo Patierno updated DISPATCH-374:
------------------------------------
    Description: 
Using the read operation with both --type and --name (or --identity) option works fine for something like a "connecto" for example.

[root@localhost /]# qdmanage -b localhost:5673 read --type connector --name BROKER
{
  "verifyHostName": true, 
  "stripAnnotations": "both", 
  "name": "BROKER", 
  "allowRedirect": true, 
  "idleTimeoutSeconds": 16, 
  "maxFrameSize": 65536, 
  "host": "127.0.0.1", 
  "cost": 1, 
  "role": "route-container", 
  "type": "org.apache.qpid.dispatch.connector", 
  "port": "5672", 
  "identity": "connector/127.0.0.1:5672:BROKER", 
  "addr": "127.0.0.1"
}

Using it for a linkRoute, address (and I guess autoLink) produces a NotFound error :

[root@localhost /]# qdmanage -b localhost:5673 read --type linkRoute --name my_queue_out
NotFoundStatus: Not Found

but executing same command without --type specified, it works well.

[root@localhost /]# qdmanage -b localhost:5673 read --name my_queue_out
{
  "name": "my_queue_out", 
  "prefix": "my_queue", 
  "connection": "BROKER", 
  "identity": "linkRoute/1", 
  "distribution": "linkBalanced", 
  "type": "org.apache.qpid.dispatch.router.config.linkRoute", 
  "dir": "out"
}

I'd like to add that trying with a non exsisting name for a connector (for example), the error is the following :

[root@localhost /]# qdmanage -b localhost:5673 read --type connector --name BROKER1
NotFoundStatus: No entity with name='BROKER1'

at same time router produce an AGENT error on the console.

It seems that the NotFoundStatus message is different for linkRoute, address (and I guess autoLink).

  was:
Using the read operation with both --type and --name (or --identity) option works fine for something like a "connecto" for example.

[root@localhost /]# qdmanage -b localhost:5673 read --type connector --name BROKER
{
  "verifyHostName": true, 
  "stripAnnotations": "both", 
  "name": "BROKER", 
  "allowRedirect": true, 
  "idleTimeoutSeconds": 16, 
  "maxFrameSize": 65536, 
  "host": "127.0.0.1", 
  "cost": 1, 
  "role": "route-container", 
  "type": "org.apache.qpid.dispatch.connector", 
  "port": "5672", 
  "identity": "connector/127.0.0.1:5672:BROKER", 
  "addr": "127.0.0.1"
}

Using it for a linkRoute, address (and I guess autoLink) produces a NotFound error :

[root@localhost /]# qdmanage -b localhost:5673 read --type linkRoute --name my_queue_out
NotFoundStatus: Not Found

but executing same command without --type specified, it works well.

[root@localhost /]# qdmanage -b localhost:5673 read --name my_queue_out
{
  "name": "my_queue_out", 
  "prefix": "my_queue", 
  "connection": "BROKER", 
  "identity": "linkRoute/1", 
  "distribution": "linkBalanced", 
  "type": "org.apache.qpid.dispatch.router.config.linkRoute", 
  "dir": "out"
}


> qdmanage: using --type option with --name (or --identity) option causes a "Not found"
> -------------------------------------------------------------------------------------
>
>                 Key: DISPATCH-374
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-374
>             Project: Qpid Dispatch
>          Issue Type: Bug
>    Affects Versions: 0.6.0
>            Reporter: Paolo Patierno
>
> Using the read operation with both --type and --name (or --identity) option works fine for something like a "connecto" for example.
> [root@localhost /]# qdmanage -b localhost:5673 read --type connector --name BROKER
> {
>   "verifyHostName": true, 
>   "stripAnnotations": "both", 
>   "name": "BROKER", 
>   "allowRedirect": true, 
>   "idleTimeoutSeconds": 16, 
>   "maxFrameSize": 65536, 
>   "host": "127.0.0.1", 
>   "cost": 1, 
>   "role": "route-container", 
>   "type": "org.apache.qpid.dispatch.connector", 
>   "port": "5672", 
>   "identity": "connector/127.0.0.1:5672:BROKER", 
>   "addr": "127.0.0.1"
> }
> Using it for a linkRoute, address (and I guess autoLink) produces a NotFound error :
> [root@localhost /]# qdmanage -b localhost:5673 read --type linkRoute --name my_queue_out
> NotFoundStatus: Not Found
> but executing same command without --type specified, it works well.
> [root@localhost /]# qdmanage -b localhost:5673 read --name my_queue_out
> {
>   "name": "my_queue_out", 
>   "prefix": "my_queue", 
>   "connection": "BROKER", 
>   "identity": "linkRoute/1", 
>   "distribution": "linkBalanced", 
>   "type": "org.apache.qpid.dispatch.router.config.linkRoute", 
>   "dir": "out"
> }
> I'd like to add that trying with a non exsisting name for a connector (for example), the error is the following :
> [root@localhost /]# qdmanage -b localhost:5673 read --type connector --name BROKER1
> NotFoundStatus: No entity with name='BROKER1'
> at same time router produce an AGENT error on the console.
> It seems that the NotFoundStatus message is different for linkRoute, address (and I guess autoLink).



--
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