Re: Connection not timing out

From: William \(Bill\) Vaughn (billvaRemoveThis_at_nwlink.com)
Date: 04/30/04 

Date: Fri, 30 Apr 2004 09:29:26 -0700

What provider are you using? Are you waiting for the connection to close
(and it doesn't)? 

-- 
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Jiho Han" <jiho.han@infinityinfo.com> wrote in message
news:uaflafsLEHA.1892@TK2MSFTNGP10.phx.gbl...
> This is a repost of my earlier question which I have not been able to
> resolve as of yet.
>
> I have two processes that must check on a single table row for access
rights
> to other table records.
> I am using Connection.IsolationLevel set to adXactSerializable to achieve
> this since I found no other way to do this (SQL server lock hints are not
> supported by my provider).
> So whichever opens a transaction will have the lock and update the mutex
row
> and proceed with its transactions.  When it completes, the other process
> then locks it using the same procedure.
>
> My problem is that the waiting process seems to wait indefinitely no
matter
> what setting I use for ConnectionTimeout or the CommandTimeout.  I am
using
> Connection.Execute to retrieve this mutex row at the beginning of the
> transaction and hold it until the end of the transaction.  The ADO doc
> states that the timout settings control the when the error occurs due to
> "delays from network traffic or heavy server use".  Does this not hold
true
> for SQL server holding the lock as well?
>
> Can someone tell me how to proceed?
> Thanks much.
>
> Jiho
>
>

Relevant Pages