Threads, Tasks and company war...

Question

0.00/5 (No votes)

See more:

Hi all,
we currently fight some kind of company war related to threading and tasks.
It's all about a service that is used here for pulling emails.
On start a thread is launched that runs the Email-Puller wich internally uses several tasks to repeadly pull emails from several accounts (each account has one task).

Recently the service threw an exception leaving everything in a "miserable state".

Now several questions came up where we could not agree on a solution that fits best practices and stuff alike.

Currently the service just shuts down if an exception occurs.
Decision makers are fine with that, how surprising...

I told them that handling needs to be implemented to shut down each running task and then the main thread that runs if an error occurs. The Main-Thread could then be restarted so that the service keeps running. Decision makers just say nah, we just restart it because of time-related issues.

Is it possible that on such a failure some tasks are not automatically shut down if the service unexpectedly stops?
Besides the fact that a shutdown will not cause data-loss due to its implementation (worst case would be that an email would be pulled twice into our system) is that an acceptable way to let an application crash and rely on its sub-tasks/threads beeing shut down automatically?

What's your opinion, I'll be happy to hear them.
best regards
Andy

Posted 20-Nov-12 22:21pm

hoernchenmeister

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Nissim Salomon · Answer 1 · 2012-11-21T08:15:00

Hi, there is a great a articale on threading here
now in my personal opinion each task must handle the exception that raising from the code been execued, meaning that the service must continue working while other threads raise exceptions. shutdown command can be issued but it must be because it has been intended