Multi threading in windows service.

Question

0.00/5 (No votes)

See more:

I am designing a solution for a client where in data has to be polled from SQL table and a request is to be sent to a WCF service with a request formed from that data. The response of the WCF service will contain additional data that has to be updated in the SQL table again.

For e.g. in TableA there are 6 columns namely primaryKeyColumn,columnA, columnB, columnC, columnD and columnE.

The WCF request will contain data from columns A,B and C.
The service response will contain data for all 5 columns.
The data of columns D and E needs to be updated for that row in the tableA.

I have thought of implementing this using Windows service. To increase the performance I am thinking to implementing multi threading in this solution.

Can some one guide me in this ? I have never used multi threading in windows service before. What are the risks ?

What I have tried:

I have created a windows service that polls the SQL database table every 15 seconds,gets the first row depending on certain condition,create the request for WCF service , call the WCF service, update the data in SQL table based on the response.
I have not implemented multi threading yet.

Posted 15-Nov-16 19:19pm

Member 12311311

Updated 15-Nov-16 21:58pm

Nelek

v2

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)

Midi_Mick · Answer 1 · 2016-11-15T19:42:00

A windows service basically has to be multithreaded if it wants to be able to do anything at all. The basic pattern (much of which is stubbed for you when you create a Windows Service) is that the main thread handles commands from the service controller (Start, Stop, Pause, and the like). The normal pattern is when the "Start" command goes through, you start off a thread that waits for some sort of IPC from your app. Included in that wait are also signals from the main thread to pause or stop the service. When an IPC comes through, depending on the sort of processing involved in the command, you can either process the command in that thread (if it's quick), or kick off another thread to process the command (if it's possible to get another command before the first is finished processing).

All the normal rules of threading apply - interrupting the processing, protecting data, etc. The only thing you don't have to worry about is marshalling to the UI thread, as there is none.