We try to reconnect to fanout (exclusive) queues

[Michael H Wilson]

According the the AMQP spec an exclusive queue should only ever be usable by a single client. In the qpid amqp impl we try to reconnect to our exclusive fanout queues when connection drops. This works most of the the time because the server auto-delete's the queue quickly enough that by the time you reconnect you are able to create a "new" queue with the same name as the old one. However, in busy environments where the broker isn't able to delete the queue quickly enough you will run into errors about not being able to bind to an exclusive queue.

The solution is fairly simple, we need to override the reconnect method in the FanoutConsumer class and use a new name instead of re-useing the old one.

The other option would be to ditch the old consumers on reconnect and create new ones, but I think the latter is cleaner.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/31718

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/31718
Committed: http://github.com/openstack/oslo-incubator/commit/719eba4cae7f2bc11753b17c65c7597b8d6ed72d
Submitter: Jenkins
Branch: master

commit 719eba4cae7f2bc11753b17c65c7597b8d6ed72d
Author: Michael Wilson <email address hidden>
Date: Thu May 23 10:27:08 2013 -0600

    Don't reconnect to exclusive fanout consumers.

    See bug #1180166, basically we shouldn't be trying to reconnect to
    exclusive queues.

    Fixes: bug #1180166
    Change-Id: I71ac5a150ea8c4d97a34404cb821ce8e8dfa152d