Connections Not Closing

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am using the data access application block running on Windows server 2003 and accessing SQL 2000 database (on the same box). I have some very simple code that is getting executed from a asp.net page. The code is calling executeNonQuery in a loop 30 times. I notice that after the code executes and I go into SQL Enterprise Manager and look at the open connections there are 30 open connections. Is there something I am missing ? I thought the application block would handle closing the connections. The other interesting thing is if I run the same code on Windows 2000 server accessing the database on the 2003 server everything works ok. Any ideas ???
 
Hi,

Are you sure these connections are the result of your testing or are there
other applications, that have also 1 or more connections open.
You could close the connectios explicitly if you aren't doing that already.
Please attach some source code, because this is a bit to vague.
You could try to use a simple console application to isolate you're problem.

Good luck





JZink said:
I am using the data access application block running on Windows server
Click to expand...
2003 and accessing SQL 2000 database (on the same box). I have some very
simple code that is getting executed from a asp.net page. The code is
calling executeNonQuery in a loop 30 times. I notice that after the code
executes and I go into SQL Enterprise Manager and look at the open
connections there are 30 open connections. Is there something I am missing
? I thought the application block would handle closing the connections.
The other interesting thing is if I run the same code on Windows 2000 server
accessing the database on the 2003 server everything works ok. Any ideas
???
 
Back
Top