I've created PROTON-2153 for this. https://issues.apache.org/jira/projects/PROTON/issues/PROTON-2153
On Wed, 2019-12-04 at 11:38 -0500, Andrew Stitcher wrote: > On Tue, 2019-12-03 at 11:47 +0000, Bourne, Mark wrote: > > 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. > > This is very definitely a bug. > > However the Reactor.get_connected_address() method is no longer the > best way to achieve what you're trying to do - use the > Connection.connect_address property instead. > > I'll fix the bug and note in the Reactor.get_connected_address() docs > that it's deprecated for Connection.connected_address. > > Andrew --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
