Multi-Threading - Cleanup strategy at program end
Posted
by weismat
on Stack Overflow
See other posts from Stack Overflow
or by weismat
Published on 2010-03-12T14:29:37Z
Indexed on
2010/03/12
15:17 UTC
Read the original article
Hit count: 338
What is the best way to finish a multi-threaded application in a clean way?
I am starting several socket connections from the main thread in seperate sockets and wait until the end of my business day in the main thread and use currently System.Environment.Exit(0)
to terminate it.
This leads to an unhandled execption in one of the childs. Should I stop the threads from the list? I have been reluctant to implement any real stopping in the childs yet, thus I am wondering about the best practice. The sockets are all wrapped nicely with proper destructors for logging out and closing, but it still leads to errors.
© Stack Overflow or respective owner