Hi Komandur,
How are you doing on this issue currently , are you still suffering this
problem? As you mentioned that since it is the webservice which makes the
store procedure call to the backend oracle db, the front client's inactive
won't notify the backend db to abort the transaction,yes? If so, have you
tried setting command timeout in the webservice method (for example, if
you're using the Command object to execute the store procedure, we can
apply a timeout on it, does this helps? In addition, I also suggest you
try posting in the ADO.NET group to see whether any guys there have some
good suggstions on this. Thanks,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
Thread-Topic: Record lock timeout with webservices
thread-index: AcV58cjpfxNVVjfSSSi8vSzNrixZHg==
X-WBNR-Posting-Host: 213.42.2.11
From: =?Utf-8?B?S29tYW5kdXIgS2FubmFu?=
<Ko************@discussions.microsoft.com>
References: <4D**********************************@microsoft.co m>
<A0**********************************@microsoft.co m>
Subject: RE: Record lock timeout with webservices
Date: Sat, 25 Jun 2005 18:53:01 -0700
Lines: 22
Message-ID: <AE**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:6941
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
Thanks for reply. We already use stored procedure for this. the webservices
calls this procedure to lock/unlock records. This webservice is used by the
portable terminals. When pdt (portables) freezes, the oracle server is not
aware that the client is done since for the oracle server the client is web
services which is alive - so i need a way to timeout this.
"Ajit" wrote:
Use transaction in strored procedure instead of web service.
"Komandur Kannan" wrote:
We have a smart device application running on handhelds(Symbol
MC9000G). The backend is Oracle and a middle tier web services development done in
Vb.net.
We use pessimistic Locking due to specific business needs
When such a lock is made for a transaction (this code is in the web
service) and the handhelds are terminated abnormally (cold booted or battery
low), the lock still remains. The Web service's connection to oracle is still
active and it does not know that the handheld using it is now inactive.
How do we timeout the transaction to unlock and roll back