I have an app that I have recently been testing to try an determine the
cause of this Timeout Expired issue. I am using the performance monitor to
check the # of connection pools as well as the # number of pooled
connections. When I start the app and the user logs in a pool & connection
is created and all is well. However when I shut down the app the pool does
not go away. Then if I start the app again another pool and connection are
created and soon, and so on??

Does anyone have any idea how I should deal with this? Should the pool
created by the app be detroyed when the app is no longer in memory.

By the way I am using CLR .Net Data for the specific app, not _global.

Re: Connection Pools by Angel

Angel
Tue Sep 16 18:07:41 CDT 2003

I am sorry, you are running into this bug

http://support.microsoft.com/default.aspx?scid=kb;en-us;314429

It does not mean that the pools are not being cleaned, the problem is with
the actual counters. This problem affects both v1.0 and v1.1.

"William Reyes" <wreyes@optonline.net> wrote in message
news:esb$krGfDHA.2352@TK2MSFTNGP12.phx.gbl...
> I have an app that I have recently been testing to try an determine the
> cause of this Timeout Expired issue. I am using the performance monitor to
> check the # of connection pools as well as the # number of pooled
> connections. When I start the app and the user logs in a pool & connection
> is created and all is well. However when I shut down the app the pool does
> not go away. Then if I start the app again another pool and connection are
> created and soon, and so on??
>
> Does anyone have any idea how I should deal with this? Should the pool
> created by the app be detroyed when the app is no longer in memory.
>
> By the way I am using CLR .Net Data for the specific app, not _global.
>
>