locking mechanism in asp.net

Question

1.00/5 (1 vote)

See more:

.NET4.5

Hi everyone,

I am new to development. I have implemented one web application. Here customer can run the .exe from clicking the one button.
We have huge number of user so we need to avoid the parallel accessing or running of exe . Please help me to implemented a locking mechanism to running the my .exe file in synchronize process (keeping in Q user requests)

Posted 19-Aug-14 2:06am

srinivas vempa

Updated 19-Aug-14 2:13am

Karthik Harve

v2

Add a Solution

Comments

ZurdoDev 19-Aug-14 11:53am

You mention web application but then also mention .exe. Not the same thing. What are you talking about?

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)

PhilLenoir · Answer 1 · 2014-08-19T04:56:00

Set up a database table with a single row and 2 fields, ID (tinyint will do) as primary key and Lock as, say, a nullable varchar.
Insert one row with ID of 1 and leave Lock null

In your code, within a try/catch block, in a loop, write an update query, updating Lock with a piece of unique information for that request (note you can make Lock a number if the unique information is numeric) where ID = 1 and Lock Is NULL
Now select the row and if Lock matches you unique information exit the loop
In the loop, after the test, sleep for a short period (say 10 milliseconds) to avoid blocking
After the loop execute your EXE
In the Finally of the try/catch block issue an update query to set lock to NULL where ID = 1 and Lock = unique information

The only danger with this approach is that somehow a process exits without ever clearing the lock. To solve this you could add a timestamp and run a scheduled job on your database to clear Lock after a timeout on that timestamp. If you are not using a DBMS server, test the timestamp in your loop and clear it if it has expired, but you still need to test to ensure that this process is the one that holds the lock.