when there is an high volume of webservice calls - this is your answer... Well... semaphore can't lock it if it is already locked... so it waits till it is free. There is a specific amount of time it can wait, then it throws such exception. It is due to dead locks (Dead lock is when two or more threads need the same resources and each of them is blocking the other work... It cause they both are waiting in an infinite loop)
2009/8/12 TomerMiz <[email protected]> > > Hi All, > > I'll be happy to get your option on this, i have a webservice that > uses Semaphore to access shared (VB) resources and i noticed that when > there is an high volume of webservice calls the semaphore could no > make locks using the WaitOne() method, when using it, it throws an > exception "Thread was being aborted." after 2 minutes. > I believe its aprobably a timeout error, but not sure what is the > cause.. > > Can someone please explain what effects the lock? why t could be > completed? what effects the timeout and can i configure somthing on > the code or IIS or machine level to prevent that? > > Thanks >
