Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have several long-running Task objects. I’d like them all to just keep running indefinitely. The job of one of these tasks is to self-monitor the system. If something happens outside of normal operating conditions, I’d like it to be able to stop running and somehow signal the other tasks to stop running as well. Is it enough to just use Task.WaitAny(), stop the one thread and the others will stop, or will those other Tasks keep running indefinitely?
Those Tasks will continue running, unless you explicitly handle cancellation.
The preferred method to handle this is using the new cooperative cancellation support in .NET 4.
The normal method would be to have a continuation on each task that runs when a task fails/faults. It could then have a
CancelationTokenSourcethat gets canceled. Each task can occasionally check to see if it should abort because a cancellation is requested.