Oracle® Data Provider for .NET Developer's Guide 11g Release 2 (11.2) Part Number E12249-01 |
|
|
View PDF |
Thread.Abort()
should not be used, as unmanaged resources may remain unreleased, which can potentially cause memory leaks and hangs.
To optimize resource usage, ODP.NET objects, such as OracleConnection
and OracleCommand
, should be explicitly closed or disposed, or both, when they are no longer needed. This should be done rather than relying on the .NET Framework garbage collector to reclaim resources. Many users have found that under stress conditions, explicit Close
or Dispose
calls result in much lower resource usage.