Oracle connection pooling

[Lenny Shprekher]

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;

 

[Guest]

Yes and no. Connection pooling is based on the entire connection string,
along with user (if integrated security). Every hit with the same connection
pools. If you have the web service in its own web, you can use the config
file to set up connection properties and be less likely to affect other
projects. With web services, it is more imperative that you Dispose()
connection objects when you are done with them.

On a related note, ODP.NET (from Oracle http://otn.oracle.com) is a better
option than OleDb. The OracleClient is okay, but there are things missing
from it (written while 9i was still in beta).


---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

 

[Lenny Shprekher]

So, how would you disable connection pooling in my case?
I saw many samples and suggestions, looks like neither of them is working
good with OleDb and Oracle. I am still having this unclosed sessions and
have to reboot IIS every week to release them. This is pain in some special
place ... please help.
(Changing code to another provider required a lot of code changes)

 

[Paul Clement]

¤ So, how would you disable connection pooling in my case?
¤ I saw many samples and suggestions, looks like neither of them is working
¤ good with OleDb and Oracle. I am still having this unclosed sessions and
¤ have to reboot IIS every week to release them. This is pain in some special
¤ place ... please help.
¤ (Changing code to another provider required a lot of code changes)
¤

I believe the connection string parameter is "OLE DB Services = -2;". This will disable Pooling and
AutoEnlistment.

I don't believe this will resolve your problem though as it would appear that connections are simply
not being terminated properly by your web service and that is why Oracle is accumulating orphaned
sessions.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)