Application blocks and connection pool errors

[Phil Townsend]

In order to help alleviate connection pool errors, we have switched to
the Microsoft Application blocks to help manange connections. Still, we
are getting problems with connection pools reaching their limit and
causing page errors. Aren't application blocks supposed to address this
issue?

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Scott Allen]

Hi Phil:

It can help, but the code using the block still has some
responsibilities. Does your app use the block to return SqlDataReader
or XmlReader objects? Those objects still need to be disposed of
properly for connection pooling to work.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Tue, 07 Dec 2004 05:49:47 -0800, Phil Townsend
<ph*******@yahoo.com> wrote:

In order to help alleviate connection pool errors, we have switched to
the Microsoft Application blocks to help manange connections. Still, we
are getting problems with connection pools reaching their limit and
causing page errors. Aren't application blocks supposed to address this
issue?

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Phil Townsend]

Generally I return DataReaders and DataSets, mostly the latter...

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Scott Allen]

Then definetly focus on the code requesting a DataReader from the
block. Make sure the code calls Dispose or Close on the returned
object even if there is an exception. (The using keyword in C# makes
this easy).

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Tue, 07 Dec 2004 12:09:29 -0800, Phil Townsend
<ph*******@yahoo.com> wrote:

Generally I return DataReaders and DataSets, mostly the latter...

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!