Re: Connection pool in WinForms app using Data Access Block is exhausting

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Teemu Keiski (joteke_at_aspalliance.com)
Date: 09/29/04 

Date: Wed, 29 Sep 2004 18:46:55 +0300

Hi,

as far as I know not (though I use the older one, v.1.0), but I've seen it
causing those when you make multiple calls to it quickly (for example use
DAAB methods in a loop, and yes we confirmed that no conns were left open)
because it creates temporarily one connection per call, unless you pass it
one as parameter (IIRC it has argument to take the conn too). Of it does the
calls quickly in a loop, it might exhaust the conn pool (because pool cannot
keep up with need of new connections as they are not freed right away on
such loop scenario)

So, the solution has been increasing the pool size for apps which use DAAB
extensively in loops etc. But definately make sure, that you don't leave any
conns open accidentally for example with datareaders (DAAB does create them
with CloseConnection but that yiu close them right away after use). That's
the first one you should check 

-- 
Teemu Keiski
MCP, Microsoft MVP (ASP.NET), AspInsiders member
ASP.NET Forum Moderator, AspAlliance Columnist
http://blogs.aspadvice.com/joteke
"Jason" <nfr@nospam.com> wrote in message
news:ur2qM6ipEHA.1712@tk2msftngp13.phx.gbl...
> I have an application that is using Microsoft's Data Access Application
> Block in a WinForms Client/Server configuration. Recently, we have been
> having problems where an application is timing out and throwing an error
> stating that the connection pool is exhausted, requiring a restart of the
> application.
>
> Is there a bug in the Application Block?
>
>

Relevant Pages