T
Thomas
Hello gurus!
I get some very weird error messages from my server after a few days of
uptime. The server is a collection of .NET remoting singlecall objects which
calls stored procedure in our SQL Server 2000. The error messages I receive
is as follow:
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.
at
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnec
tionString options, Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String
connectionString, CommandType commandType, String commandText,
SqlParameter[] commandParameters) in C:\Program Files\Microsoft Application
Blocks for .NET\Data Access
v2\Code\CS\Microsoft.ApplicationBlocks.Data\SQLHelper.cs:line 881
at GP.Services.DB.ComputerDB.SayHello(...) in
e:\_projects\gp\server\gpservices\dbproxy\computerdb.cs:line xxx
If anyone has ran into this before and possibly could point me in the right
direction for solving this issue, I would be very grateful. It sure looks
lika som connectionpooling issues, and as you can see I tried with the Data
ApplicationBlock from microsoft but no difference. I close all my
connections in a finally block. Thanks in advance
// Thomas Örnmarker
Gamers Paradise
I get some very weird error messages from my server after a few days of
uptime. The server is a collection of .NET remoting singlecall objects which
calls stored procedure in our SQL Server 2000. The error messages I receive
is as follow:
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.
at
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnec
tionString options, Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String
connectionString, CommandType commandType, String commandText,
SqlParameter[] commandParameters) in C:\Program Files\Microsoft Application
Blocks for .NET\Data Access
v2\Code\CS\Microsoft.ApplicationBlocks.Data\SQLHelper.cs:line 881
at GP.Services.DB.ComputerDB.SayHello(...) in
e:\_projects\gp\server\gpservices\dbproxy\computerdb.cs:line xxx
If anyone has ran into this before and possibly could point me in the right
direction for solving this issue, I would be very grateful. It sure looks
lika som connectionpooling issues, and as you can see I tried with the Data
ApplicationBlock from microsoft but no difference. I close all my
connections in a finally block. Thanks in advance
// Thomas Örnmarker
Gamers Paradise