Hi Lenny,
It's very likely that connection pooling is happening if you are using a
fixed connection string. Connection pooling is normally just fine for
stateless web services - is there any reason you are having an issue? For
instance, if you are trying to keep a connection open across different web
service calls from your caller side to the service side, this could be a
design issue you want to remedy.
As for connection pooling - different drivers allow different options.
Typically there is a connect string option to disable/enable connection
pooling.
If you have a properly designed statless service, there would not normally
be issues associated with connection pooling. Since you should be striving
to make each call stateless, I'm not sure why you would be having a problem.
Regards
Dan Rogers
Microsoft Corporation
--------------------
From: "Lenny Shprekher" <le*******@yahoo.com>
Subject: Oracle connection pooling
Date: Thu, 9 Dec 2004 11:22:20 -0500
Lines: 16
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Message-ID: <OB**************@TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host:
www.bessemer.com 198.160.35.2
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.phx.gbl!TK2MSFTNGP10
.phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices:7999
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
Hi,
I am getting issues that Oracle collecting opened sessions (connections)
from my webservice using regular System.Data.OleDb.OleDbConnection object.
I am guessing that this is connection pooling issue. Is there is any way to
disable connection pooling for one particular .net webservice?
Thanks,
Leonid
BTW: Here is sample connection string we are using:
Provider=MSDAORA.1;Password=test;User ID=test;Data Source=test.tcp;