This is a cherrypick of oslo-incubator:
55678c7ab7fbc1b2beb428d046bb4162f23b0a53
From the oslo-incubator bug:
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/60483 github. com/openstack/ ceilometer/ commit/ 43a892138a50625 7992a116d2d33d3 914c95e406
Committed: http://
Submitter: Jenkins
Branch: stable/havana
commit 43a892138a50625 7992a116d2d33d3 914c95e406
Author: Eoghan Glynn <email address hidden>
Date: Thu Dec 5 22:16:55 2013 +0000
Properly reconnect subscribing clients when QPID broker restarts
Fixes bug 1251757
This is a cherrypick of oslo-incubator: bc1b2beb428d046 bb4162f23b0a53
55678c7ab7f
From the oslo-incubator bug:
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.
Change-Id: If966bb25e49b58 37293a1bb181bbb 02086599d81