[rabbitmq-discuss] RabbitMQ .NET client 3.2.3 bug?

Michael Klishin mklishin at gopivotal.com
Mon Feb 24 03:45:29 GMT 2014

On 23 Feb 2014, at 17:51, Steve T <ssteo at roboqa.com> wrote:

> I'm using RabbitMQ .NET client 3.2.3 with RabbitMQ 3.2.3 but encountering some random errors thrown from within the client itself. The error below happens very occassionally during item publishing via my own function EnqueueItem();
> Stack Trace:
> System.Net.Sockets.SocketException: The descriptor is not a socket
>   at System.Net.Sockets.Socket.SetSocketOption (SocketOptionLevel optionLevel, SocketOptionName optionName, Int32 optionValue)
>   at System.Net.Sockets.TcpClient.set_ReceiveTimeout (Int32 value)
>   at RabbitMQ.Client.Impl.SocketFrameHandler_0_9.set_Timeout (Int32 value)
>   at RabbitMQ.Client.Impl.ConnectionBase.ClosingLoop ()

This is a known problem. Like Jonathan suggests, you will largely avoid it by not connecting
every time you want to publish a message. RabbitMQ client connections are supposed to
be long lived.


Software Engineer, Pivotal/RabbitMQ

More information about the rabbitmq-discuss mailing list