.Net Data Provider for Oracle

[Bobbie]

We have downloaded the new .Net Data Provider for Oracle. It accesses the
Oracle (Unix) database just fine - updates and retrieves data. The problem
we are having is with the connections being closed. We understand that this
provider does not support connection pooling. But it seems that the Connection.close
command does not close the connections. The result is that in a short time
we exceede our maximum allowed connections to the database.

In the Windows app, the connections seem to close more often. We are guessing
that when this app closes that Garbage collection runs. However, in our
Web app, the connections never close.

Do we need to use the Dispose method? Is there someting else we are missing.

Any ideas would be appreciated!

[PWilmarth]

If you can't use the close method, then my immediate thought is to use dispose;
you just can't guarantee when it the garbage collector will dispose of
it.

[Bobbie]

"PWilmarth" <pwilmarth80231@msn.com> wrote:
>
>If you can't use the close method, then my immediate thought is to use dispose;
> you just can't guarantee when it the garbage collector will dispose of

>it.

We added the dispose to every procedure that had an 'open' connection. The
connections still just sat there open, even after the web page had been closed
for 10 to 15 minutes.