ASP.NET
Posted: Tue 15 Dec 2009 17:58
I am runnig a WebSite on a IIS 6.0 and with i looking at the number of sessions that are open and in some moments its getting over 30 sessions.
This is my connectionString:
I have several ways i use a OracleConnection in my code:
1) Using the OracleDataSource directly in my aspx page: This is not open or close by code. It uses the web.config ConnectionString.
2) Opening connections at runtime (in order to use packages):
OracleConnection gets Open and Close at runtime usign the ConnectionString from the web.config.
3) Using the LINQ: I create the DataContext passing the ConnectionString from the web.config.
Does every connection being obtained from the pool or can they be opened independtly? If so, how can i avoid this behaviour?
This is my connectionString:
I have several ways i use a OracleConnection in my code:
1) Using the OracleDataSource directly in my aspx page: This is not open or close by code. It uses the web.config ConnectionString.
2) Opening connections at runtime (in order to use packages):
OracleConnection gets Open and Close at runtime usign the ConnectionString from the web.config.
3) Using the LINQ: I create the DataContext passing the ConnectionString from the web.config.
Does every connection being obtained from the pool or can they be opened independtly? If so, how can i avoid this behaviour?