IIS Application Pool and .NET Garbage Collection

Question

Consider an ASP.NET application with a connection pool memory leak problem (where connections, for example, do not close correctly).

Does the application pool recycle the pool connection pool (so more connections can be made)?

If the connections remain in memory until the garbage collector deletes them, will this happen when the application pool restarts (or can they leave them further)? I also understand that the garbage collector can clean them at any time, but are still in use and cannot be collected until restarting reset or application pool?

I am looking at a system in which the ultimate goal, obviously, is to correctly correct the code for proper connection management, and I am trying to get more information about the garbage collection / application process.

Answer 1

Yes, disposing of the application pool kills and restarts the IIS process responsible for starting your application. All resources are freed at this stage simply because the process ends.

, . , , , . Dispose() ( "" ), , , .

Answer 2

- . - ( ) . , , ; .

Close Dispose , . , , . , , , . Dispose - using, Dispose .

ADO.NET 2.0 : ClearAllPools ClearPool. , .