[
https://issues.apache.org/jira/browse/PROTON-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-2153.
-------------------------------------
Fix Version/s: proton-c-0.30.0
Resolution: Fixed
> Python Proton Reactor get_connection_address attempts to call non-existent
> connection.get_address method
> --------------------------------------------------------------------------------------------------------
>
> Key: PROTON-2153
> URL: https://issues.apache.org/jira/browse/PROTON-2153
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
> Affects Versions: proton-c-0.29.0
> Environment: Centos 7 with the following packages installed:
> - epel-release # To make the following packages from EPEL available
> - python36
> - python36-qpid-proton
> - qpid-cpp-server
> - qpid-tools
> Versions of packages related to Qpid:
> $ yum list installed | grep qpid
> python2-qpid.noarch 1.37.0-4.el7 @epel
> python2-qpid-qmf.x86_64 1.39.0-1.el7 @epel
> python36-qpid-proton.x86_64 0.29.0-1.el7 @epel
> qpid-cpp-client.x86_64 1.39.0-1.el7 @epel
> qpid-cpp-server.x86_64 1.39.0-1.el7 @epel
> qpid-proton-c.x86_64 0.29.0-1.el7 @epel
> qpid-qmf.x86_64 1.39.0-1.el7 @epel
> qpid-tools.noarch 1.39.0-1.el7 @epel
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
> Priority: Major
> Fix For: proton-c-0.30.0
>
> Attachments: demo.py
>
>
> Pasted from [email protected]:
> {quote}With Python Proton version 0.29.0, the `get_connection_address` method
> of `proton.reactor.Reactor` attempts to call `connection.get_address()`.
> However, that method doesn't seem to exist, leading to an exception. Code to
> reproduce this is attached (demo.py - also copied at the end of this message
> in case this mailing list strips attachments). In this example, we already
> know the broker address so it's not really necessary to use
> `get_connection_address`, but our actual messaging handler holds connections
> to multiple brokers and we use `get_connection_address` to work out which one
> a message has come from.
> It's possible that we're not using `get_connection_address` as intended, but
> this has worked in previous versions of Proton to get the address of the
> broker from which a message was received. This was working with Proton
> 0.26.0, but breaks with 0.29.0. text{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
