[rabbitmq-discuss] dotnet client background thread

[Eyal Post]

We have an issue with a .net client application that creates a connection in order to publish message and caches this connection in a variable. The problem is that when the program exits, it gets stuck in memory because there is an AMQP thread that doesn't exit.
I'm not sure how the RabbitMQ threads are created but in .net there is an option to set a thread as a background thread and in this case when the application closes it will not wait for background threads to stop. Is the .net client setting the background threads it creates background? If not, can you change that?
See here for more details: http://msdn.microsoft.com/en-us/library/system.threading.thread.isbackground.aspx

Eyal Post


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20111215/1ccc9674/attachment.htm>