title: How can I solve a connection pool problem between ASP.NET and SQL Server?
body: <p>The last few days we see this error message in our website too much:</p>
  <blockquote>
  <p>&quot;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.&quot;</p>
  </blockquote>
  <p>We have not changed anything in our code in a while. I revised the code to check open connections which didn't close, but found everything to be fine.</p>
  <ul>
  <li><p>How can I solve this?</p>
  </li>
  <li><p>Do I need to edit this pool?</p>
  </li>
  <li><p>How can I edit this pool's max number of connections?</p>
  </li>
  <li><p>What is the recommended value for a high traffic website?</p>
  </li>
  </ul>
  <hr />
  <h3>Update:</h3>
  <p>Do I need to edit something in IIS?</p>
  <h3>Update:</h3>
  <p>I found that the number of active connections are anywhere from 15 to 31, and I found that the max allowed number of connections configured in SQL server is more than 3200 connections, is 31 too many or should I edit something in the ASP.NET configration?</p>