Dynatrace Hub
Connection Pools: TomcatConnection Pools: Tomcat
Application server method of pooling and sharing connections to a database.
Extension by Dynatrace
- Product information
- Release notes
Overview
Several OneAgent extensions provide insight into connection pool performance and issues such as connection leaks. The extensions cover the following technologies: Apache Tomcat, Oracle WebLogic, IBM WebSphere Application Server, IBM WebSphere Liberty, and Red Hat JBoss and Wildfly.
Use cases
This extension collects connection pool performance, usage and availability metrics for Tomcat.
Prerequisites:
- Tomcat process that runs on a supported Linux or Windows operating system.
- OneAgent version 1.273+
- Dynatrace version 1.273+
To get metric insight:
- Install OneAgent on the virtual machine or server of your Tomcat process.
- Activate the OneAgent feature
Java Metric Extensions 2.0 (JMX). - Select in this same tile Add to environment to configure the extension.
- Open the Tomcat Connection Pool Overview dashboard.
copy to clipboard
Extension content
Content typeNumber of items included
metric query
1
screen metric tables
1
screen injections
1
screen chart groups
2
generic relationship
1
metric metadata
15
dashboards
1
screen layout
1
list screen layout
1
generic type
1
screen entities lists
1
Feature sets
Below is a complete list of the feature sets provided in this version. To ensure a good fit for your needs, individual metrics can be activated and deactivated by your administrator during configuration.
Feature setsNumber of metrics included
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Borrowed connections | tomcat.connectionPool.borrowedConnections | - | Count |
| Reconnected connections | tomcat.connectionPool.reconnectedConnections | - | Count |
| Released connections | tomcat.connectionPool.releasedConnections | - | Count |
| Returned connections | tomcat.connectionPool.returnedConnections | - | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Max active connections | tomcat.connectionPool.maxActive | Maximum amount of active connections allowed concurrently | Count |
| Max idle connections | tomcat.connectionPool.maxIdle | The maximum number of connections that should be kept in the pool at all times | Count |
| Max wait time | tomcat.connectionPool.maxWait | The maximum number of milliseconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception | Millisecond |
| Minimum idle | tomcat.connectionPool.minIdle | The minimum number of established connections that should be kept in the pool at all times | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Active connections | tomcat.connectionPool.activeConnections | Currently used connections | Count |
| Created connections | tomcat.connectionPool.createdConnections | Number of connections created | Count |
| Idle connections | tomcat.connectionPool.idleConnections | Number of open but unused connections | Count |
| Abandoned connections | tomcat.connectionPool.removeAbandoned | Number of connections that have not been properly released | Count |
| Abandoned connection timeout | tomcat.connectionPool.removeAbandonedTimeout | Timeout before an abandoned connection can be removed | Second |
| Waiting connection requests | tomcat.connectionPool.waitCount | Number of connection requests currently waiting | Count |
Full version history
To have more information on how to install the downloaded package, please follow the instructions on this page.
ReleaseDate
EF1 to EF2 Tomcat Connection Pool conversion:
- Add Tomcat connection pool entity and its relation to the tomcat process
- Custom unified analysis screen for Tomcat connection pools
- Metric chart injection into Process Group Instance screen
- Overview dashboard for Tomcat connection pools
- Add feature sets to control included metrics
- New metric func:tomcat.connectionPool.availableConnections that shows the current available connections
- All metrics have changed key from the EF1 version. The prefix builtin:tech.tomcat has been removed. This is a breaking change for any configuration you had which used the metric key, such as metric events.