ASP.net to SQL server , connection not closing even after Log out

[thomson]

Hi all,
In my application i use efficient use of the DAL, but for eg
4 users has been connected to the application, it shows 4 connections
established, when all the users logout, and again logs in it shows 8
connections established, What should i do inorder to release all my
connections when i logout, even though in my application i have closed
the connections appropriately

Thanks in Advance

thomson

 

[Edwin Knoppert]

I'm curious of a session.abandon will help..
?

 

[thomson]

iam using Session.Abandon(), while the user logs out, but still the
connection is not getting closed


Regards

thomson

 

[Jason Kester]

Why would you expect database connections to close themselves?
Anything you open will remain so until you explicitly close it. If you
end a request with that database connection still alive, it will sit
there awaiting further instructions forever (or until garbage
collection gives up on it, which is essentially forever in machine
time.)

If you don't want your code to leak, wrap every database connection in
a using{} block and explicitly close it when you have finished your
operation. Otherwise, you'll see exactly what you're seeing from your
"efficient" DAL!

Jason Kester

 

[Edwin Knoppert]

Your topic title versus contents confused me.
Like the other responded, you should close every connection.
The IDisposed stuff might be a help as well.
I'm using a class which on destruction frees the connection it made.
I can force that but i can also wait until ISS destroys it.
Since then no more odd events.

At first, i thought you where talking about user (http)connections.