Web.Config file - Pooling=off

Hi,

We have dotnet c# website - VS2010 . If users connection we are getting below error . Upon checking in DB for every user it opens around 10 session ( by using (sp_who2). We are going thru the codes page by page to identify the DB connection related. In order to close all DB connection from applciation after it is used by application- can we use " Pooling=false' -- in web.config.

After setting this 'Pooling=false' - the error is not appearing. But want to know - will it create any issue, please advice. Tx

-------------------------------

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL.

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

O. Developer10y ago
tx
Rajeev Punhani10y ago
Hi,

First of all to check the exact error place the above custom error settings in web.config file.

Remove the Pooling="false" .I think you will get the following error
"The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached".Setting Pooling to false will not create a pool of connection rather than it will create a new object of connection every time.This will cause a memory leak related issue. By default there are 100 connections in a pool.Just use using block where ever you are using database connection then those will be automatically disposed.