Recently, one of my teams was facing a connection timeout issue when we tried to implement 'parallelism' in a data-driven application.
A colleague of my mine pointed out that there was a bug in ADO.NET (with a mirrored SQL Server) that could result in this wierd behavior. More details available at this link.
Quick resolution is to try increasing the connection timeout and allocate a greater no of connections at start-up in the pool.
A colleague of my mine pointed out that there was a bug in ADO.NET (with a mirrored SQL Server) that could result in this wierd behavior. More details available at this link.
Quick resolution is to try increasing the connection timeout and allocate a greater no of connections at start-up in the pool.
No comments:
Post a Comment