S
Shailesh Humbad
Many a page has ADO Connection objects that were opened but never
closed. The Connection object allocates its own resources when it is
opened. When the object goes out of scope without being explicitly
closed, the resources ASP allocated for it are freed, but the resources
it allocated on its own are not. These eventually clutter up the server
and slow it down to a crawl. My question is, is there a way to track
down these orphaned resources and forcibly free them from ASP, without
restarting IIS or the server? Or does one have to wait for the unused
Connections to time out and release themselves? I know that good coding
practice is best, but is there a temporary fix to tidy up these
connections left open?
Shailesh
closed. The Connection object allocates its own resources when it is
opened. When the object goes out of scope without being explicitly
closed, the resources ASP allocated for it are freed, but the resources
it allocated on its own are not. These eventually clutter up the server
and slow it down to a crawl. My question is, is there a way to track
down these orphaned resources and forcibly free them from ASP, without
restarting IIS or the server? Or does one have to wait for the unused
Connections to time out and release themselves? I know that good coding
practice is best, but is there a temporary fix to tidy up these
connections left open?
Shailesh