469,903 Members | 2,046 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,903 developers. It's quick & easy.

manually closing DB connections...required?

We're running into a problem on our new site. Once a week or so, our site
goes down with an 'out of memory error'. Rebooting the web server fixes
things. Googling the error doesn't return many results (one, actually) and
the suggested fix is to make sure you are manually closing all DB
connections. I'm doing that now, but I had thought that asp.net had fairly
robust automated cleanup, and that having to explicitely close every
connection wasn't necessarily needed (though I certainly agree that it's
good practice). Just curious as to what .net's clean-up capabilities
actually are.

-Darrel
Nov 18 '05 #1
7 1264
Hi darrel,

It's not a matter of .Net's cleanup capabilities. It's a matter of the
nature of database connections in .Net. What I mean is that it has nothing
to do with global .Net operations, such as garbage collection. It is
specific to database connections, due to their nature. You will find the
same type of thing with .Net classes that open and close files, and use
unmanaged resources "under the hood". For example, if you open a file, you
had better close it, or it will become unusable (until the next reboot).
Why? Because that's how the file system works. It locks files when they are
opened, and unlocks them when they are closed. A database connection is
similar, in that, you can open it and it will remain open (and in memory)
until you close it. While the connection at your end may be unused when
you're finished using it, it is still connected to the database at the other
end. Closing it disconnects it, allowing it to be cleaned up.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
I get paid good money to
solve puzzles for a living

"darrel" <no*****@hotmail.com> wrote in message
news:u0**************@TK2MSFTNGP12.phx.gbl...
We're running into a problem on our new site. Once a week or so, our site
goes down with an 'out of memory error'. Rebooting the web server fixes
things. Googling the error doesn't return many results (one, actually) and
the suggested fix is to make sure you are manually closing all DB
connections. I'm doing that now, but I had thought that asp.net had fairly
robust automated cleanup, and that having to explicitely close every
connection wasn't necessarily needed (though I certainly agree that it's
good practice). Just curious as to what .net's clean-up capabilities
actually are.

-Darrel

Nov 18 '05 #2
> While the connection at your end may be unused when
you're finished using it, it is still connected to the database at the other end. Closing it disconnects it, allowing it to be cleaned up.


While we're on this topic...is there a log anywhere or any way to see the
current open DB connections?

-Darrel
Nov 18 '05 #3
> While the connection at your end may be unused when
you're finished using it, it is still connected to the database at the other end. Closing it disconnects it, allowing it to be cleaned up.


Yikes! Wow...we screwed this one up, then. ;o)

Ok, I'm halfway through closing all our connections. This is definitely the
problem (and our fault). Thanks for clarifying that for me!

-Darrel
Nov 18 '05 #4
Oh...one more question...what is the '= nothing' for, and is that something
I should have as well?

For instance, I had:

objConnect.open()

I am now adding:
objConnect.close()

but should I also add:

objConnect = nothing

-Darrel
Nov 18 '05 #5
Hi Darrel,

The following .Net SDK article should be helpful. Along with describing
Connection Pooling, it provides several performanc counters that you can use
to view Connections:

http://msdn.microsoft.com/library/de...taProvider.asp

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
I get paid good money to
solve puzzles for a living

"darrel" <no*****@hotmail.com> wrote in message
news:#R**************@tk2msftngp13.phx.gbl...
While the connection at your end may be unused when
you're finished using it, it is still connected to the database at the

other
end. Closing it disconnects it, allowing it to be cleaned up.


While we're on this topic...is there a log anywhere or any way to see the
current open DB connections?

-Darrel

Nov 18 '05 #6
Hi Darrel,

No, that' s not necessary.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
I get paid good money to
solve puzzles for a living

"darrel" <no*****@hotmail.com> wrote in message
news:Od*************@TK2MSFTNGP09.phx.gbl...
Oh...one more question...what is the '= nothing' for, and is that something I should have as well?

For instance, I had:

objConnect.open()

I am now adding:
objConnect.close()

but should I also add:

objConnect = nothing

-Darrel

Nov 18 '05 #7
> Hi Darrel,

No, that' s not necessary.


Thanks, Kevin!

-Darrel
Nov 18 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

8 posts views Thread by simon place | last post: by
4 posts views Thread by dustin lee | last post: by
3 posts views Thread by Anthony | last post: by
1 post views Thread by C Sharp beginner | last post: by
3 posts views Thread by blakecaraway | last post: by
13 posts views Thread by Simon Harvey | last post: by
7 posts views Thread by Tumurbaatar S. | last post: by
7 posts views Thread by Martien van Wanrooij | last post: by
1 post views Thread by Waqarahmed | last post: by
reply views Thread by Salome Sato | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.