[rabbitmq-discuss] .NET client: intermittent AlreadyClosedException - connected host has failed to respond

Fri Dec 21 19:29:10 GMT 2012

Hi Emile,

Is there any plan to solve this AlreadyClosedException issue in the
future release?

I am using RabbitMQ 2.8.6 with .NET client on Windows Server 2008 R2. 
Our system also suffers from this AlreadyClosedException problem. 
It causes our system to retry the related task, and this degraded the
performance.

Thanks,
Bin Chen

-----Original Message-----
From: rabbitmq-discuss-bounces at lists.rabbitmq.com
[mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Emile
Joubert
Sent: Monday, December 03, 2012 2:11 AM
To: Andrei Volkov
Cc: Discussions about RabbitMQ
Subject: Re: [rabbitmq-discuss] .NET client: intermittent
AlreadyClosedException - connected host has failed to respond

Hi Andrei,

On 29/11/12 18:15, Andrei Volkov wrote:
> It looks like a TCP port exhaustion on the client side.
> What happens is, unlike our main app, our healthcheck page opens (and
> closes) a new connection every time it is hit. The healthcheck page is

> hit every 5 seconds. By default on Windows the ephemeral TCP port 
> can't be reused until after 240 seconds after it's closed. Hence the 
> port exhaustion.

That explanation would work if there were only 48 ports available in the
ephemeral range. By default there are many more, so I would be surprised
if this was the cause.

-Emile

_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss