[rabbitmq-discuss] RabbitMQ .NET client 3.2.3 bug?
ssteo at roboqa.com
Mon Feb 24 15:21:05 GMT 2014
Ok, thanks. Is there any property or method in the RabbitMQ .NET client
that allows me to check if the connection is still alive? Let's say if
RabbitMQ server got restarted, etc. how do I recreate my connection ?
On Mon, Feb 24, 2014 at 11:45 AM, Michael Klishin <mklishin at gopivotal.com>wrote:
> 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
> > 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
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss