Re: pooled connections and the statechangeevent
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Tue, 9 Oct 2007 15:35:17 -0400
Brian wrote:
I have an asp.net application that uses pooled connections.
There was no way for you to know it (except maybe by browsing through
some of the previous questions in this newsgroup before posting yours -
always a recommended practice) , but this is a classic ADO newsgroup.
ADO.Net bears very little resemblance to classic ADO so, while you may
be lucky enough to find a dotnet-knowledgeable person here who can
answer your question, you can eliminate the luck factor by posting your
question to a group where those dotnet-knowledgeable people hang out. I
suggest microsoft.public.dotnet.framework.adonet.
So, there
may be connections that exist even after my particular use of the
connection object is disposed.
If, for some reason a pooled connection is not used in a long enough
period of time that the database closes the connection, does the
pooling connection manager monitor the statechangeevent and remove
this connection from the pool (or automatically re-establish it)?
Or...do I need to worry about having dead connections from the
connection pool?
There is no need to worry about it. Closed connections are not retained
in the pool. Typically connections are closed by the pool manager long
before the database manager.
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
.
- Prev by Date: Re: ADODB.Stream.Open now with VS2005 gives wrong type error message
- Next by Date: Re: ADODB.Stream.Open now with VS2005 gives wrong type error message
- Previous by thread: Re: Timeout Error: Data Adaptor
- Next by thread: Memory consumption
- Index(es):
Relevant Pages
|
|
