Montoyafan
New Member
Sorry if this is a duplicate, i've read many questions that are either very similar or require roughly the same keywords to describe (but aren't quite the same)...situation: an asp.net application has a connection pool memory leak problem (where connections are not being closed correctly for example)...I need clarity on the following
oes recycling the application pool clear the connection pool (thus allowing more connections to be made)?If the connections are left in memory until the Garbage Collector removes them...does this happen when the application pool is restarted (or are/can they left beyond that)? I also understand the Garbage Collector could clean them up at anytime as well...but are they still in use and unable to be collected until a reset or application pool restart?i'm reviewing a system and the end goal is obviously to have the code corrected to manage the connections correctly, but i'm trying to gain more of an understanding about the garbage collection/application pool process...Thanks heaps!
oes recycling the application pool clear the connection pool (thus allowing more connections to be made)?If the connections are left in memory until the Garbage Collector removes them...does this happen when the application pool is restarted (or are/can they left beyond that)? I also understand the Garbage Collector could clean them up at anytime as well...but are they still in use and unable to be collected until a reset or application pool restart?i'm reviewing a system and the end goal is obviously to have the code corrected to manage the connections correctly, but i'm trying to gain more of an understanding about the garbage collection/application pool process...Thanks heaps!