PoolExhaustedException vs. Connection Settings

[VSVcamunda]

Hi all!
We experience the problem with PoolExhaustedException when running Camunda connected to Oracle DB. At some point Camunda stops working because of this error.
org.apache.tomcat.jdbc.pool.PoolExhaustedException: [pool-3-thread-1544] Timeout: Pool empty. Unable to fetch a connection in 30 seconds, none available[size:100; busy:100; idle:0; lastwait:30000].
The problem could be resolved by restarting the Camunda server but we need to get rid of this error as it keep appearing.

Is it related to the number of connections which is set in ‘server.xml’? We tried maxTotal=“50” and maxTotal=“100” but still eventually get the error. Does it has sense to increase this number? Is it safe?

Sometimes we also get the error “ORA-29270: too many open HTTP requests”. Is it related to PoolExhaustedException?

Thank you,
Sergey

[cpbpm]

Please check the forum on similar topic. Connection pool issue is already addressed for multiple db vendors on tomcat server configuration. Please check the parameters like testOnBorrow,validationQuery and validationInterval

Here is one of the steps,

Why Tomcat need to restart every day?

We had several issues with MySQL connection. Our final stable configuration for the resource is given bellow. As already mentioned above we had added testOnBorrow, validationQuery and validationInterval. But the other issue has appeared which has been fixed with jdbcInterceptors. <Resource name="jdbc/ProcessEngine" auth="Container" type="javax.sql.DataSource" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" uniqueResourceName="process-engine" …

Please do recheck your configuration and update the community.