Menu
The tomcat connection pool has a setting called maxActive and a setting called maxIdle my questions are.
For some reason the docs are not making sense to me. maxActive and maxIdle exist on both the apache dbcp and the tomact 7 jdbc-pool according to the docs at http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html
maxActive (int) The maximum number of active connections that can be allocated from this pool at the same time. The default value is 100
maxIdle (int) The maximum number of connections that should be kept in the pool at all times. Default value is maxActive:100 Idle connections are checked periodically (if enabled) and connections that been idle for longer than minEvictableIdleTimeMillis will be released. (also see testWhileIdle)
872
maxIdle. (int) The maximum number of connections that should be kept in the pool at all times. Default value is maxActive : 100 Idle connections are checked periodically (if enabled) and connections that been idle for longer than minEvictableIdleTimeMillis will be released. (
maxActive: The maximum number of active connections that can be allocated from this pool at the same time. The default value is 100.
The number of connections in the connection pool should be equal the number of the exec threads configured in WebLogic. The rationale is very simple: If the number of the connections is less than the number of threads, some of the thread maybe waiting for a connection thus making the connection pool a bottleneck.
After going through all the resources, tomcat JDBC and HikariCP seem to be reliable and faster than other two connection pools.
maxActive is straight forward. maxIdle can be explained in this way - say you have 100 max Active connections and say you set maxIdle to 80. Assuming there are no requests going to the database, only 80 connections will be tested (via the validationquery) and will stay active. The other 20 will be closed. So at any point you can only have 80 idle connections.
You might want to set this to be a different number to prevent additional (unnecessary) connections going out to the database. Cos every connection that is served by the database consumes resources (like memory).
But, assuming you have set the maxActive size to 100 and all 100 are in use almost all the time, this setting will obviously not matter.
109
the maximum number of active connections that can be allocated from this pool at the same time. This attribute is used to limit the number of connections a pool can have open.
(int) The maximum number of connections that should be kept in the pool **at all times.** This is to limit the idle connections. The connections(not larger than the value of maxIdle) will not be released so that the next request for connections will be much faster.
So in a word, maxActive is to limit max connections.
But idle(maxIdle or minIdle) is more for performance issue(exchange time with space/resources) , among which, the maxIdle is to limit the max connections(the resources) that you are going to exchange time with.
30
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
