[rabbitmq-discuss] Federation Many Connections?

James Carr james.r.carr at gmail.com
Tue Mar 27 18:20:24 BST 2012

One last note (I feel so spammy today) is that it stops generating new
connections when I go and define the exchange on the upstream server
that was missing it. The previous connections however stick around.


On Tue, Mar 27, 2012 at 11:00 AM, James Carr <james.r.carr at gmail.com> wrote:
> Finally, here's my configuration in case it helps reproduce the
> problem: https://gist.github.com/61a55a37e9c2e77d1797
> Thanks,
> James
> On Tue, Mar 27, 2012 at 10:57 AM, James Carr <james.r.carr at gmail.com> wrote:
>> The issue persists with version 2.8.1 as well. It seems to work okay
>> when a single downstream connects to the upstream, but when a cluster
>> connects to the upstream the node making the connection creates new
>> direct connections to itself each time it fails to bind to the
>> upstream exchange.
>> Attached is a screenshot from the management console and here is the
>> contents of my log file: https://gist.github.com/b8714347f97a86b34724.
>>  The interesting thing to note is that the number of errors in the log
>> file correspond directly to the number of direct connections
>> dc2rabbitmq5 makes to itself (I cleared the logs before retrying
>> again).
>> Thanks,
>> James
>> On Tue, Mar 27, 2012 at 10:38 AM, James Carr <james.r.carr at gmail.com> wrote:
>>> So I investigated why it seems that one of the nodes in my test
>>> cluster wind up have hundreds of direct connections to itself lately.
>>> It turned out that  one of the upstreams it was connecting to didn't
>>> have the exchange that is meant to be federated defined. It seems that
>>> when the exchange doesn't exist on the upstream it just periodically
>>> keeps retrying but does't close the previous connection.
>>> I can send more log details if needed. I am currently running 2.8.0
>>> but will upgrade to 2.8.1 and see if the problem persists.
>>> Thanks,
>>> James

More information about the rabbitmq-discuss mailing list