Min Pool Size Option?

Question

Hi Guys
We have having problems with connection pools remaining in a production environment.
We have of course checked to make sure that all objects are closed and disposed and all connections close correctly in our dev and test environments.
In most cases each user only every opens one connect to the database from a ASP.NET application running in IIS 6.0 (.Net Framework 1.1) using Oracle Data Access Components 10.2.0.2.20. These connections appears to remain for days and in the case where multiple connections they appear to slowly close and again leave the single remaining connection open for days.
Any ideas do we need to set the Min Pool Size to Zero?
How long should it take to close connections that are not in use?
Sample code...
Private Sub btODPConnect_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btODPConnect.Click
Dim strConn As String
Dim mConn As New Oracle.DataAccess.Client.OracleConnection
strConn = "Password=" & txtPassword.Text & ";User ID=" & txtUsername.Text & ";Data Source=" & txtDatabase.Text & ";Min Pool Size=0;"
mConn = New Oracle.DataAccess.Client.OracleConnection(strConn)
mConn.Open()
If mConn.State = ConnectionState.Open Then
ASPNET_MsgBox("Connection Open!")
End If
mConn.Close()
mConn.Dispose()
mConn = Nothing
End Sub
Thanks in advance P

Answer 1

What problem are you trying to solve at this point? Simply "why is odp not tracing?" The only suggestions I really have there are
1) make sure you restart the app after enabling tracing parameters
2) make sure the directory you've set tracing to is open as far as permissions
3) make sure you've set tracing in the right registry setting if you have multiple versions of ODP installed
4) if you're trying to write to c:\ root, try creating and pointing to a different (c:\odptrace for example) directory instead.
Hope it helps,
Greg