September 30, 2002 at 6:32 pm
Hi,
I don't know whether this is the right forum to post this question to but I
will give it a try. I have an asp.net page which connects to the db a number
of times and each time retrieves a number of datareaders (with
CommandBehavior.CloseConnection set).
When I check the sql server management
section after I run and unload the page and look at the process info and/or lock/processid there are a number of processes associated with asp.net
framework. Does this mean that my connections are not being closed after the
reader is destroyed? The connection is closed implicitely once the reader is destroyed, and actually I don't get a pooling error when I loop that section of code, something that would happen eventually if the connections were open.
The lock/process is released after a short time.
Thanks in advance.
Edited by - suaaddaa on 09/30/2002 6:33:15 PM
October 3, 2002 at 12:29 pm
This is an anwer that I got elsewhere:
What you may be seeing is the connection pooling
trying to maximize connection availablity and instead of creating/destroying
connections constantly it creates several connections that to pool through.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply