Connection Pool Issue
From: Guadala Harry (ChipsNSalsa_at_gh.com)
Date: 06/11/04
- Next message: MauricioDG: "RE: Confirm Delete popup from a LinkButton in a repeater"
- Previous message: Angel: "Re: Setting Control Properties before postback"
- Next in thread: bruce barker: "Re: Connection Pool Issue"
- Reply: bruce barker: "Re: Connection Pool Issue"
- Reply: Rob T: "Re: Connection Pool Issue"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 11 Jun 2004 10:37:22 -0700
I have an ASP.NET/C# app that connects to SQL Server 2000. I recently
started getting the following error message during development (i.e., when
launching the app from the VS.NET 2003 IDE):
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.
I've found that closing and re-opening VS.NET clears things up. What's
going on? What can I do to prevent this? Am I doing something bad? I thought
the connection pool manages itself and recycles connections as necessary.
Thanks,
GH
- Next message: MauricioDG: "RE: Confirm Delete popup from a LinkButton in a repeater"
- Previous message: Angel: "Re: Setting Control Properties before postback"
- Next in thread: bruce barker: "Re: Connection Pool Issue"
- Reply: bruce barker: "Re: Connection Pool Issue"
- Reply: Rob T: "Re: Connection Pool Issue"
- Messages sorted by: [ date ] [ thread ]