Problem with ASP.NET Session in SQL Server and Connection Pooling

[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

[bruce barker \(sqlwork.com\)]

the error means close is not being called on the connection. be sure you
have no code that uses the same connection string. also check that you have
no trouble connecting to dc for authenication.

-- bruce (sqlwork.com)
"RyoSaeba" <ry******@mail2Air.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...

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

[RyoSaeba]

bruce barker (sqlwork.com) wrote:

the error means close is not being called on the connection. be sure you
have no code that uses the same connection string. also check that you have
no trouble connecting to dc for authenication.

Thanks for the answer!
For the other application connection to Sql Server I use a different
connection string/pool and I have checked that every time the
connection is correctly closed.
I think that this problem is only of the Connection Pool used for the
Asp.net Session management.
But is it correct to define a connection pool in the string
"sqlConnectionString" of the "sessionState" section of Web.config? Or
for the sessionState is better don't define a connection pool in the
connection string?
Thanks.
Ryo

>
"RyoSaeba" <ry******@mail2Air.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...

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