Oracle connections

Posts   
 
    
alex
User
Posts: 68
Joined: 30-Mar-2004
# Posted on: 25-Jan-2005 21:38:18   

Hi,

I've noticed that some connections to the Oracle database still exist with the "inactive" status after the DataAccessAdapter object is out of scope and, I assume, is disposed. I've verified that when I create an Adapter with the pKeepOpened parameter set to true, I use the CloseConnection at the end. If I don't use the pKeepOpened parameter, my understanding is that LLBLGen closes the connection right after the statement is executed.

So, why if I check Oracle sessions after my app is closed, I still see the connections from the ASP.NET? Is this a result of connection pooling? These connections go away after I restart the IIS.

Please help me to understand why it works this way or how to remove the connections that are not used any more.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39933
Joined: 17-Aug-2003
# Posted on: 25-Jan-2005 22:46:18   

That's connection pooling simple_smile Connection pooling is actually keeping open a physical connection which is re-used among threads. So when dbconnection.Open is called, you actually get an open connection from the pool mapped into the ado.net connection object.

Frans Bouma | Lead developer LLBLGen Pro