C# Semaphore issue

noashira

Hi All,

I'll be happy to get your opinionn this, i have a webservice that uses Semaphore to access shared (VB) resources and i noticed that the semaphore could not 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

Plater

The 2minutes is probably IISs page timeout. When it hits that it aborts the thread that is running the page code.
If your page is really waiting longer then that, you might want to consider changing how things work. I cannot imagine waiting that long for a webpage

noashira

thanks for your reply
see the code example

Expand|Select|Wrap|Line Numbers

 
          try

            {

                semCollectionLock.WaitOne();

                bDidLock = true;
 
                string sKey;
 
                stSoapObject = scSystemObject.GetObject()
 
                // unlock collection

                semCollectionLock.Release();
 
            }

            catch (Exception e)

            {

                if (bDidLock)

                {

                    try

                    {

                        semCollectionLock.Release();

                    }

                    catch

                    {

                        StaticMethods.WriteErrorToLog(MethodName, "Get - Error Releasing Semaphore..." + sSessionKey, iRandom);

                    }

                }
 
            }

            return stSoapObject;

--------------------

The object that is returned (stSoapObjet) is then running a very long process, and when the second thread arrives it hangs on WaitOne

C# Semaphore issue

re: C# Semaphore issue

re: C# Semaphore issue

Similar .NET Framework bytes

/bytes/development

/bytes/it

/bytes/about