[PROTON-2153] Python Proton Reactor get_connection_address attempts to call non-existent connection.get_address method

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-c-0.29.0
• Fix Version/s: proton-c-0.30.0
• Component/s: python-binding

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

• Assignee: Andrew Stitcher
• Reporter: Andrew Stitcher
• Created: 04/Dec/19 18:54
• Updated: 16/Dec/19 10:52
• Resolved: 04/Dec/19 19:39

Description

Pasted from [e-mail]:

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