Size is reached, which in this case is 30 connections. The connection pool will only increase until the max pool Those 10 connections are in use it will increase the pool by 5 moreĬonnections. In this example it sets up a pool of 10 connections to start with. "Incr Pool Size=5 Decr Pool Size=2 Max Pool Size=30 " +
"Min Pool Size=10 Connection Lifetime=120 Connection Timeout=60 " + OracleConnection con = new OracleConnection() Ĭon.ConnectionString = "User Id=scott Password=tiger Data Source=oracle " + To solve this problem you must set in connection string some parameters: So far, i'm not 100% sure if this problem is due to ODP.net provider or asp.net IIS setting Hopefully my description is clear enough to well shape the problem. Net framework project in win2k server for the past few years. Finally = Can any expert provide me a suggestion regarding the problem? I strongly believe that there sure have a solution for it since many ppl have inplemented. i wonder if i should do anything in the processmodel I tried to turn off the session in web.config but the problem is still there. Pratical in operating environment ? I suspect this are some configuration errors in asp.net state management or IIS settings.
By refering to discussion in Oracle OTN forum, some of the guys said turning off the connnection pool will solve the problem. But I do not think this is a practical solution in order to solve the problem in real time. Some Temporary Solutions = By referring to the Google forum, in order to kill this "Never ended" oracle connections, what I need to do is to restart the WWW service in Window Component I have checked the Oracle Enterprise Management Console which showing that the aspnet_wp processes are running even closing up any ASPX web app browser They do happen in WinXP pro and Win2k Pro for IIS 5.X (haven't tried in win2k server). We did close and dispose the connection object as shown in oracle ODP.net samples(in Since we r using the same data access base classes for Window and Web apps, there is not possible for the error to happen alone in web App. These eventually bring us to oracle connections used up situation :( Based on my experiment, The problem will not occur while running Window app or ASPX app using Problem Description = One thing I feel strange is that every time the ASPX applicationĮnded (closed and disposed the connection object), the Oracle session connection never killed. Currently we are using Microsoft.NET Framework 1.1 (VS.net IDE 2003) in our C# project. Thx :-) Introduction = We are using ODP.net (version 9.2.0.4.01) asĭata provider for Oracle in our dotnet app. I have been posting this question in google group and still no cannot find a suitable solution for it.
0 kommentar(er)
