R
RyoSaeba
Hello,
I have a problem with the session state set to Sql Server (AspNet 1.1,
Windows Server 2003 on an Application Center cluster, Sql Server 2000
on another server).
Sometimes, when many user are using the application, we got this
error:
"System.Web.HttpException: Unable to connect to SQL Server session
database. ---> System.InvalidOperationException: Timeout expired. 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."
Is it safe/recommended to set a connetion pool in the Session
connection string in Web.config?
Actually I have put this definition in the Web.config:
<sessionState
mode="SQLServer"
sqlConnectionString="data source=xxx.xxx.xxx;user
id=xxx;password=xxx;connection reset = true;connection lifetime =
15;enlist=true;min pool size=1;max pool size=200;"
cookieless="false"
timeout="2" />
Thanks in advance!
Ryo
I have a problem with the session state set to Sql Server (AspNet 1.1,
Windows Server 2003 on an Application Center cluster, Sql Server 2000
on another server).
Sometimes, when many user are using the application, we got this
error:
"System.Web.HttpException: Unable to connect to SQL Server session
database. ---> System.InvalidOperationException: Timeout expired. 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."
Is it safe/recommended to set a connetion pool in the Session
connection string in Web.config?
Actually I have put this definition in the Web.config:
<sessionState
mode="SQLServer"
sqlConnectionString="data source=xxx.xxx.xxx;user
id=xxx;password=xxx;connection reset = true;connection lifetime =
15;enlist=true;min pool size=1;max pool size=200;"
cookieless="false"
timeout="2" />
Thanks in advance!
Ryo