qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chuck Rolke (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DISPATCH-189) Dispatch python tools fail to detect rejected connection
Date Wed, 28 Oct 2015 21:23:27 GMT
Chuck Rolke created DISPATCH-189:

             Summary: 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:
 Client sends 
 Router sends 
    Close(Arguments: Error: {
      Condition: 'amqp:resource-limit-exceeded',
      Description: 'connection disallowed by local policy',
      Info: ''}

Then the qdstat tool fails with message:
AttributeError: 'ConnectionClosed' object has no attribute 'url'

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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message