title: C3P0 maxPoolSize exhausted
body: <p>I have an application that uses C3P0 for connection pooling. It has been working fine for a long time, but recently i am getting the following exception while trying to hit the database.</p>
  
  <pre><code>com.amazon.carbonado.FetchException: com.mchange.v2.resourcepool.TimeoutException: A client timed out while waiting to acquire a resource from com.mchange.v2.resourcepool.BasicResourcePool@1bdc777 -- timeout at awaitAvailable()
  </code></pre>
  
  <p>Upon googling I found that this is due to maxPoolSize being exhausted. I increased the pool size from 25 to 100 to check if it is the reason. It was fixed temporarily, but some time later i am seeing the error again while attempting db connection (there werent any other db connection requests at that time). When i check the DB for active/inactive connections there is just 1 entry from the machine in v$session. Yet i am receiving this error. I donot understand where the connections are used ?</p>
  
  <p>Can some one tell me why this could be happening. Also what does the maxPoolSize in C3P0 represent ? Is it that DB connections that can be checked out?</p>
  
  <p>Also does the poolSize represent the actual dbConnections ?</p>