Connection pool problems

[Lloyd Sheen]

I am running into the connection pool running out of connections problem.

Error msg is :
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.

Do sp_who on SQL Server 2000 shows only the connection for QA and 2 other
connections. The SQL Server is on a local workstation so I can monitor what
is going on. I changed the connection string to be:
<add key="ConnectionString"
value="server=localhost;Trusted_Connection=true;database=Commerce;Min Pool
Size=5;Max Pool Size=1000" />

That does not make any change. So this means that I do about 10 connections
before the app shuts down by not allowing any other connections.

HELP

Lloyd Sheen

 

[Ken Dopierala Jr.]

Hi Lloyd,

It could be that the number of connections for the OS is being used up.
This is just a suggestion hopefully someone else can clarify. I know W2K
Pro allows up to 10 connections, after that it refuses them. Whether or not
it counts connections to SQL server I don't know. I do know IIS connections
count as well as connections to resources like printers. If anything this
could give you information to search on for a solution. Of course, if you
are using a Server version of 2000 or 2003 then this wouldn't apply. Good
luck! Ken.