title: Oracle Error: Pooled connection request timed out
body: <p>Im using Oracle12c with the application written in C# and using Oracle.ManagedDataAccess.dll to handle the DB Connection. </p>
  
  <p>A product we have has started to occasionally throw this exception after running fine for years:</p>
  
  <pre><code>Oracle.ManagedDataAccess.Client.OracleException (0xFFFFFC0C): Pooled connection request timed out
     at OracleInternal.ConnectionPool.PoolManager`3.Get(ConnectionString csWithDiffOrNewPwd, Boolean bGetForApp, String affinityInstanceName, Boolean bForceMatch)
     at OracleInternal.ConnectionPool.OraclePoolManager.Get(ConnectionString csWithNewPassword, Boolean bGetForApp, String affinityInstanceName, Boolean bForceMatch)
     at OracleInternal.ConnectionPool.OracleConnectionDispenser`3.Get(ConnectionString cs, PM conPM, ConnectionString pmCS, SecureString securedPassword, SecureString securedProxyPassword)
     at Oracle.ManagedDataAccess.Client.OracleConnection.Open()
  </code></pre>
  
  <p>I know the cause of this error. Looking at the code neither the OracleConnection or the OracleCommand objects are being disposed. So these connections are building up until it eventually throws this exception. </p>
  
  <p>The fix is straight forward. Wrap these in <code>Using</code> statements. I dont need help with that. </p>
  
  <p>However my interests me is why this problem has started now. This software was running for years without issue. They did some database maintenance, updated other software on the same server, then this problem started. I dont know what Db maintenance they did. </p>
  
  <p>The connection string in the application does not specify any pool attributes.</p>
  
  <p>Is there a oracle db setting which would cause a lower amount of simultaneous connections in the database that could have caused this to start occurring?</p>
  
  <p><strong>UPATE</strong></p>
  
  <p>I wrote a little test app to check the limit. 
  It just loops around and opens a connection, performs a basic query and doesnt dispose the connection. 
  On my test system it starts throwing this exception after 640ish loops. It varies give or take 10 loops each time i run it. </p>
  
  <p>What is setting this limit?</p>