[rabbitmq-discuss] .net client foreground threads

Emile Joubert emile at rabbitmq.com
Tue Dec 10 10:46:18 GMT 2013


On 10/12/13 02:58, Bicubic wrote:

> My issue is that I have connections and threads lingering after abnormal
> program termination when there was no opportunity to explicitly close
> connections.

Sockets have the linger option set by default when closing. I assume
that's not the what you are referring to.

> I intended to capture this case with DomainUnload or ProcessExit
> events, however they don't fire exactly because rabbitmq is holding
> foreground threads. How should I deal with this? I don't care about
> losing messages after my application enters this state, I need a fast
> clean shutdown.

The library should not prevent your application from exiting if all
connections are shut down. Can you identify the foreground threads that
cause a problem, or supply a stacktrace?


More information about the rabbitmq-discuss mailing list