You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by jelmerterwal <gi...@git.apache.org> on 2017/04/24 12:01:32 UTC
[GitHub] tomcat issue #54: Respect minimum pool size
Github user jelmerterwal commented on the issue:
https://github.com/apache/tomcat/pull/54
For an application I develop, I see a drop in connections. The screenshot show different values of the connection pool.
Legend for the colours;
- grey -> pool size
- greenish -> idle connections
- orange/red -> connections in use
- purple -> waiting for a connection
The application uses dropwizard (www.dropwizard.io) which internally uses Tomcat's JDBC Pool. The application has 4 instances. The graph shows the sum of these instances for the number of connections.
- min size of idle connection is set to 10 (so should be 10 x 4 = 40)
- the decrease happens due abandoning of connections
The documentation indicates a minimum pool of idle connections should be available. It scared me when I first saw this happening.
```
minIdle
(int) The minimum number of established connections that should be kept in the pool at all times. The connection pool can shrink below this number if validation queries fail. Default value is derived from initialSize:10 (also see testWhileIdle)
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org