title: ADO.Net Connection pool max pool size reached
body: <p>I've inherited a .net/web service project that has serious connection object leaks. Oddly enough it's been in production for quite some time with no problems until recently. I guess the garbage collector cleans them up fairly quickly ordinarily. One web server at one customers site has started running out of connections when under heavy load. </p>
  
  <p>Obviously the solutions is to fix all the connection leaks, but that's not going to happen quickly. I can't even change the max pool setting in the connection string, the connection string is built dynamically by the app. This would require a code change which requires going through a process which is not quick.  </p>
  
  <p>Is there anything I can do at the server to mitigate this until a code change can happen? </p>
  
  <p>Why would this be a problem at just one location, a smaller location at that? If I knew the answer to that question I might be able to figure out a temporary work around.  </p>
  
  <p>Is it possible the actual problem is something else entirely and it's causing a connection pool problem? For example, perhaps the load balancing on the servers is hosed or something wrong with the web server that is having the problem.</p>