WCF Service concurrency hadnling

Question

I'am designing a winform application which should works in a redundant Environement (Main and Backup).

Both applications have to run 7/7 24/24, they connect in backend to an ODATA service to get list of objects.

what i want to achieve is to lock the object entry to be processed then just one application( first one get order to send command) handles it and continue the process.

Here what i am guessing to do .

design method AcquireLock that give one of the following values to the object to be handled : AcquireLock_Attempt = to be set in first line of code of AcquireLock method. AcquireLock_ACK = if the object was not locked by a concurrent application. AcquireLock_NAK = either the object was already locked or an error has been occured.

Please don't hesitate to share with me your experience if you already face similar scenarion.

N.B : 1- my Service is configured to Per-call. 2- the treatment between acquiring the lock and setting new state (Cmd_Send_OK, Failed_Transaction, ..) can be in range of millisecond to seconds).

_7/7 24/24_? You mean 24/7? – Grant Thomas Oct 03 '13 at 10:27 — Grant Thomas, Oct 03 '13 at 10:27

score 0 · Answer 1 · edited May 23 '17 at 12:29

0

Your question is not very clear to me but for locking individual objects from list I suggest using sql server objects table row locking within/during critical section transaction (even read): its inter-process and allow you to handle large lists of objects. See discussion here

edited May 23 '17 at 12:29

Community

1
1

answered Oct 03 '13 at 10:43

SalientBrain

2,431
16
18

i'am using Mysql DBMS – xPridex Oct 03 '13 at 11:05

score 0 · Answer 2 · answered Oct 03 '13 at 10:45

0

Your WCF service could be decorated with

[ServiceBehavior(InstanceContextMode = InstanceContextMode.Single, ConcurrencyMode = ConcurrencyMode.Single)]

answered Oct 03 '13 at 10:45

schglurps

1,387
1
14
26

And use Monitor.Lock or similar for each object/id? And this is locking for one process – SalientBrain Oct 03 '13 at 11:39

WCF Service concurrency hadnling

2 Answers2