Application blocks and connection pool errors

  • Thread starter Thread starter Phil Townsend
  • Start date Start date
P

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?
 
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.
 
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).
 
Back
Top