Connection Pool Problem

[henley.steve]

Hello,

I have a problem with an application wherein the code as designed
originally was not ensuring closing of connections when the application
encountered an exception.

I have fixed this and lesson learned there (ALWAYS enclose your
connections in a TRY or a USING).

Now, however, the pool appears to be reestablishing these connections
every time the application starts up.

I understand that asp version 2.0 has functions available to flush the
pool. However, I am using standard .NET 2003 and am therefore unable
to use asp 2.0 - or at least that is the way I understand it.

However, I have thus far been unable to locate any way to flush the
pool. They don't seem to want to timeout and I don't wish to redo the
application. Every pool thread is taken up by the application.

If anyone knows how I can flush the connection pool, I would appreciate
it.

Note: This application is running on the same machine as the Database
server.

Thanks,
Steven Henley

--
henley.steve
------------------------------------------------------------------------
Posted via http://www.codecomments.com
------------------------------------------------------------------------

[Mike Brind]

henley.steve wrote:

Hello,

I have a problem with an application wherein the code as designed
originally was not ensuring closing of connections when the application
encountered an exception.

I have fixed this and lesson learned there (ALWAYS enclose your
connections in a TRY or a USING).

Now, however, the pool appears to be reestablishing these connections
every time the application starts up.

I understand that asp version 2.0 has functions available to flush the
pool. However, I am using standard .NET 2003 and am therefore unable
to use asp 2.0 - or at least that is the way I understand it.

However, I have thus far been unable to locate any way to flush the
pool. They don't seem to want to timeout and I don't wish to redo the
application. Every pool thread is taken up by the application.

If anyone knows how I can flush the connection pool, I would appreciate
it.

Note: This application is running on the same machine as the Database
server.

Thanks,
Steven Henley

Before making posts to a news group, it is a good idea to read some of
the ones that are already there. There are two reasons for this - the
first is that your question may have been asked and answered quite
recently by other people. The second reason is to establish whether
the group you are posting to is relevant for your question.

If you had done this, you would quite quickly have come across the
following advice to previous posters:

This group covers classic ASP. Dotnet is a different technology. Try
posting your question to microsoft.public.dotnet.framework.aspnet.

--
Mike Brind