Connection pool timeout

  • Thread starter Thread starter John Rempel
  • Start date Start date
J

John Rempel

I have an ASP.NET application written in framework version 1.0.3705 and it's
been running for over a year without issues. I just moved it to a new
Windows Server 2003 machine with the 1.0 framework installed beside the
default 1.1 and now I periodically get this message:

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.

The bottom of the error page indicates that the framework version is
1.1.4322. Is there a compatibility issue between the two versions?

How can I tell the app to use the older version since it is installed as
well?

TIA,
John
 
I rarely state anything unequivocally now-a-days as there (usually) are
exceptions. There's another opportunity to cause this problem (although I
agree that not closing Connections is the 99% case). While not as frequent,
if the pooled connection dies (several reasons here), it might be orphaned
in the pool for some time. This means the pool fills to overflowing because
it's not being drained correctly. I understand that the next version of the
framework addresses this issue.

hth

--
____________________________________
Bill Vaughn
MVP, hRD
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
 
The timeout error can occur because of 2 reasons:
1. Because of a vulnerablility in SQL Server 2000. You
should install SQL Server Service pack 3 to patch up the
problem

2. You can also check, for which particular query or
stored procedure timeout error is occurring. The default
timeout for SqlCommand object is 30 seconds, if your
stored procedure or query takes more time than 30 seconds
then you will have to increase the timeout property of
command object to a higher value.

Hope this solves the problem
 
Ah, no. This is not a query timeout but a connection timeout.

--
____________________________________
Bill Vaughn
MVP, hRD
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
 
Back
Top