Properly reconnect subscribing clients when QPID broker restarts
When the QPID broker is restarted (or fails over), subscribed clients
will attempt to re-establish their connections. In the case of fanout
subscriptions, this reconnection functionality is broken. For version
1 topologies, the clients attempt to reconnect twice to the same
exclusive address - which is illegal. In the case of version 2
topologies, the address parsing is broken and an illegal address is
created on reconnect. This fix avoids the problem by removing the
special-case reconnect code that manages UUID addresses; it is
unnecessary as the QPID broker will generate unique queue names
automatically when the clients reconnect.
Reviewed: https:/ /review. openstack. org/57700 github. com/openstack/ oslo.messaging/ commit/ ffa5c077c98f548 9b978f63c507793 839e8f2a7d
Committed: http://
Submitter: Jenkins
Branch: master
commit ffa5c077c98f548 9b978f63c507793 839e8f2a7d
Author: Kenneth Giusti <email address hidden>
Date: Fri Nov 15 15:24:37 2013 -0500
Properly reconnect subscribing clients when QPID broker restarts
When the QPID broker is restarted (or fails over), subscribed clients
will attempt to re-establish their connections. In the case of fanout
subscriptions, this reconnection functionality is broken. For version
1 topologies, the clients attempt to reconnect twice to the same
exclusive address - which is illegal. In the case of version 2
topologies, the address parsing is broken and an illegal address is
created on reconnect. This fix avoids the problem by removing the
special-case reconnect code that manages UUID addresses; it is
unnecessary as the QPID broker will generate unique queue names
automatically when the clients reconnect.
Closes-bug: #1251757 8c7c5468db6bcde 10f6cf1b318
Change-Id: I6051fb503663bb