[
https://issues.apache.org/jira/browse/DISPATCH-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322151#comment-15322151
]
Paolo Patierno commented on DISPATCH-374:
-----------------------------------------
I have just checked that the same is valid for "delete" operation.
[root@localhost /]# qdmanage -b localhost:5673 delete --type address --name
my_address_name
NotFoundStatus: Not Found
[root@localhost /]# qdmanage -b localhost:5673 delete --type address --name
my_queue_in
NotFoundStatus: Not Found
no AGENT error on the router side.
Without --type option it works.
[root@localhost /]# qdmanage -b localhost:5673 delete --name my_address_name
(with no output on the console)
at same time if I tried it with a wrong "connector" name for example.
[root@localhost /]# qdmanage -b localhost:5673 delete --type connector --name
BROKER1
NotFoundStatus: No entity with name='BROKER1'
it shows a more complete NotFoundStatus and the router shows an AGENT error.
Thu Jun 9 08:31:14 2016 AGENT (error) Error dispatching Message(address=None,
properties={'operation': 'DELETE', 'type':
'org.apache.qpid.dispatch.connector', 'name': 'BROKER1'}, body={},
reply_to='amqp:/_topo/0/Router.A/temp.tfhMrWEbkVGQ+54', correlation_id=1L): No
entity with name='BROKER1'
Traceback (most recent call last):
File
"/usr/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 790, in receive
status, body = self.handle(request)
File
"/usr/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 815, in handle
target = self.find_entity(request)
File
"/usr/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 906, in find_entity
raise NotFoundStatus("No entity with %s" % attrvals())
NotFoundStatus: No entity with name='BROKER1'
> 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 "connector" 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: [email protected]
For additional commands, e-mail: [email protected]
