Hi Guys,<div><br></div><div>Every since upgrading to v2.7.1 we've found that the RabbitMQ driver has been killing our applications by throwing unhandled exceptions in background threads. �Here are two stack traces that brought down one of our test apps:</div>
<div><br></div><div><div>[2012-01-06 21:13:36,193] [ERROR] Unhandled Exception</div><div>System.Net.Sockets.SocketException: The descriptor is not a socket</div><div>� at System.Net.Sockets.Socket.SetSocketOption (SocketOptionLevel optionLevel, SocketOptionName optionName, System.Object optionValue) [0x00000] in <filename unknown>:0</div>
<div>� at System.Net.Sockets.TcpClient.set_LingerState (System.Net.Sockets.LingerOption value) [0x00000] in <filename unknown>:0</div><div>� at RabbitMQ.Client.Impl.SocketFrameHandler_0_9.Close () [0x00000] in <filename unknown>:0</div>
<div>� at RabbitMQ.Client.Impl.ConnectionBase.FinishClose () [0x00000] in <filename unknown>:0</div><div>� at RabbitMQ.Client.Impl.ConnectionBase.HeartbeatReadLoop () [0x00000] in <filename unknown>:0</div><div>
� at System.Threading.Thread.StartUnsafe () [0x00000] in <filename unknown>:0</div></div><div><br></div><div>[2012-01-06 21:13:20,706] [ERROR] Unhandled Exception</div><div><div>System.ObjectDisposedException: The object was used after being disposed.</div>
<div>� at System.Net.Sockets.Socket.SetSocketOption (SocketOptionLevel optionLevel, SocketOptionName optionName, System.Object optionValue) [0x00000] in <filename unknown>:0</div><div>� at System.Net.Sockets.TcpClient.set_LingerState (System.Net.Sockets.LingerOption value) [0x00000] in <filename unknown>:0</div>
<div>� at RabbitMQ.Client.Impl.SocketFrameHandler_0_9.Close () [0x00000] in <filename unknown>:0</div><div>� at RabbitMQ.Client.Impl.ConnectionBase.FinishClose () [0x00000] in <filename unknown>:0</div><div>� at RabbitMQ.Client.Impl.ConnectionBase.HeartbeatReadLoop () [0x00000] in <filename unknown>:0</div>
<div>� at System.Threading.Thread.StartUnsafe () [0x00000] in <filename unknown>:0</div></div><div><br></div><div>This happens on both windows and mono 2.10.1 and never seems to originate in any of our code.</div><div>
<br></div><div>Thanks,</div><div>Bryan</div>