[
https://issues.apache.org/jira/browse/PROTON-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986160#comment-14986160
]
ASF subversion and git services commented on PROTON-1035:
---------------------------------------------------------
Commit 4f5e18a059d1e0ced5b5f3ae8c9fa4503dde43fc in qpid-proton's branch
refs/heads/master from [~chug]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=4f5e18a ]
PROTON-1035: ConnectionClosed handler uses proper fields for signaling event.
Before this patch:
AttributeError: 'ConnectionClosed' object has no attribute 'url'
After this patch:
ConnectionClosed: Connection 0.0.0.0:21002 closed due to:
Condition('amqp:resource-limit-exceeded', 'connection disallowed by local
policy')
> [proton-c] Python binding mishandles connection close event
> -----------------------------------------------------------
>
> Key: PROTON-1035
> URL: https://issues.apache.org/jira/browse/PROTON-1035
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
> Affects Versions: 0.10
> Environment: qpid-dispatch tool qdstat client
> Reporter: Chuck Rolke
> Assignee: Chuck Rolke
>
> 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.
> This issue was originally reported under DISPATCH-189
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
