I have a similar problem to several other people who have posted here - I can only open up to <Max Pool Size> connections.  After that I get a timeout expired exception.

Looking at the open / pooled connections in perfmon (in both SQL Server stats, and the CLR runtime), there are never more than 5 / 6 connections open, but without fail, I cannot open more than <Max Pool Size> connections, even when I change this value or don't specify it.

I have already tried several suggested solutions - disabling SQL Server debugging in VS.net, running in release mode, connecting to several other databases on several other computers, but nothing seems to have any effect.  I have gone through the code with a fine tooth-comb, and put "open connection" counters into my database class (all the connections are opened and closed by a single pair of shared functions - and yes, the connection object is passed by ref.), and ensured that the connections are actually reporting they are closed (via SqlConnection.State) both inside and outside the function that closes them.

I'm all out of ideas now.  Any suggestions would be greatly appreciated.

--------------------------------
From: Rory Smith

-----------------------
Posted by a user from .NET 247 (http://www.dotnet247.com/)

<Id>gdTZqEcYx0eoUbAQReEUNQ==</Id>

Just to make sure I understand your scenario: you set max pool size to say
500, and you cannot open more than 500 connections? if that's the case,
that's intentional, we won't allow the application to open more connections
than the maximum set for the pool. If your issue is that you can open less
connections than the number you set there, then that's bad, and a call-stack
might help identify the problem.

I have a similar problem to several other people who have posted here - I
can only open up to <Max Pool Size> connections.  After that I get a timeout
expired exception.

Looking at the open / pooled connections in perfmon (in both SQL Server
stats, and the CLR runtime), there are never more than 5 / 6 connections
open, but without fail, I cannot open more than <Max Pool Size> connections,
even when I change this value or don't specify it.

I have already tried several suggested solutions - disabling SQL Server
debugging in VS.net, running in release mode, connecting to several other
databases on several other computers, but nothing seems to have any effect.
I have gone through the code with a fine tooth-comb, and put "open
connection" counters into my database class (all the connections are opened
and closed by a single pair of shared functions - and yes, the connection
object is passed by ref.), and ensured that the connections are actually
reporting they are closed (via SqlConnection.State) both inside and outside
the function that closes them.

I'm all out of ideas now.  Any suggestions would be greatly appreciated.

--------------------------------
From: Rory Smith

-----------------------
Posted by a user from .NET 247 (http://www.dotnet247.com/)

<Id>gdTZqEcYx0eoUbAQReEUNQ==</Id>

5 open connections is the limitation when you have MSDE version of SQL
Server.


I have a similar problem to several other people who have posted here - I
can only open up to <Max Pool Size> connections.  After that I get a timeout
expired exception.

Looking at the open / pooled connections in perfmon (in both SQL Server
stats, and the CLR runtime), there are never more than 5 / 6 connections
open, but without fail, I cannot open more than <Max Pool Size> connections,
even when I change this value or don't specify it.

I have already tried several suggested solutions - disabling SQL Server
debugging in VS.net, running in release mode, connecting to several other
databases on several other computers, but nothing seems to have any effect.
I have gone through the code with a fine tooth-comb, and put "open
connection" counters into my database class (all the connections are opened
and closed by a single pair of shared functions - and yes, the connection
object is passed by ref.), and ensured that the connections are actually
reporting they are closed (via SqlConnection.State) both inside and outside
the function that closes them.

I'm all out of ideas now.  Any suggestions would be greatly appreciated.

--------------------------------
From: Rory Smith

-----------------------
Posted by a user from .NET 247 (http://www.dotnet247.com/)

<Id>gdTZqEcYx0eoUbAQReEUNQ==</Id>

No, the MSDE has the same open connection limits as SQL Server. Only
concurrent workloads are governed where there are more than 8 of them.

HTH,

Show quoteHide quote

C# and ADO.Net - Cheap Question!
A question about closing the SqlDataReader
Can't find stored procedure
Excel and ADO.NET
return OleDbDataReader from static function