[
https://issues.apache.org/jira/browse/DISPATCH-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke closed DISPATCH-189.
--------------------------------
Resolution: Not A Problem
The faulty code is in qpid-proton and not in qpid-dispatch.
> Dispatch python tools fail to detect rejected connection
> --------------------------------------------------------
>
> Key: DISPATCH-189
> URL: https://issues.apache.org/jira/browse/DISPATCH-189
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Management Agent
> Affects Versions: 0.5
> Environment: qdstat tool connecting to broker/router that rejects the
> connection
> Reporter: Chuck Rolke
> Assignee: Chuck Rolke
>
> Case 1: connection rejected by qdrouterd:
> -----
> Testing out policy-based connection rejection shows qdstat tool
> mis-interpreting the connection failure. The order of events on the wire is:
> {noformat}
> Client sends
> Open
> Router sends
> Open
> Close(Arguments: Error: {
> Condition: 'amqp:resource-limit-exceeded',
> Description: 'connection disallowed by local policy',
> Info: ''}
> {noformat}
> Then the qdstat tool fails with message:
> {noformat}
> AttributeError: 'ConnectionClosed' object has no attribute 'url'
> {noformat}
> The expectation is for the tool to show the condition/description from the
> Close performative.
> Case 2: connection rejected by Apache Qpidd C++ broker
> -----
> When Qpidd rejects a connection it summarily closes the connection with a TCP
> FIN and does not exchange AMQP Open. In this case the qdstat tool displays a
> reasonable message about connection failure to $management.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
