Printable View
how come when I execute the close command from my app, my connection stays open. I've used:
objcon.close
objcon.dispose
objcon = nothing
when I look in Oracle my connection seems to stay open for about 30 seconds after the close command is executed, then closes...shouldn't they close right away when the close command is executed in the app?
when I logon I have four separate connections. One to check if the server is running..one to validate userid...another to validate password and another to make sure they are using the right database....is there a way I can do this with one connection in .net?
with regards to first post......is this part of connection pooling? Where you can use the same connection again and again even tho you may think it has been closed?
Not exactly sure if this is right so would like to hear what others think??? :confused:
I came across the same thing. The connection will disappear if you close your app right?
I think it is Connection Pooling. But make sure that you are closing all of your connections. In my case, I did a .open and then used an adapter, which leaves the connection in the state that it was in - and I thought it would close it, but it wasn't. Talk about connections! WOW!
If you know you will never reuse the connection you can turn pooling off by add the following at the end of your connection string:
VB Code:
If you do that then it will dissapear.
connection pooling is the way forward!!! It means you don;t have to open 1 connection when the app starts and then close it when it finishes.
You can open and close the connection as much as you want and the time delay will be minimal.
I added pooling=false at the end of my connection string and it gave me another connection:(
VB Code: