Connection Pools JBoss extension
- Latest Dynatrace
- Extension
- Published Oct 27, 2025
Collect the connection pool performance, usage and availability metrics for JBoss, identify potential issues with the utilization of the connection pool, and monitor both Non-XA and XA connection pools.
Get started
Overview
Connection Pools allow you to monitor connection pool performance and identify issues such as connection leaks.
Several built-in OneAgent extensions provide an insight into the 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
- Collect the connection pool performance, usage and availability metrics for JBoss.
- Identify potential issues with the connection pool utilization.
- Monitor both Non-XA and XA connection pools.
Compatibility information
- Jboss process that runs on a supported Linux or Windows operating system.
- Enabled statistics for JBoss EAP 6 / Application Server 7 and later.
- OneAgent version 1.273+
- Dynatrace version 1.273+
Activation and setup
- Install OneAgent on the virtual machine or server of your JBoss 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 JBoss Connection Pool Overview dashboard.
Details
This extension package contains :
- JMX data source configuration for metric ingestion.
- Topology and relationship definitions for JBoss Connection Pools and JBoss XA Connection Pools, as well as relationship definitions for connection pools and process group instances.
- A dashboard offering a monitoring overview of JBoss Connection Pools.
- A unified analysis page for each entity.
This extension is built on top of the new Extension 2.0 Framework.
Licensing anc cost
This extension queries for data every minute. Once data is produced, this is ingested as metric datapoints and is subjected to license consumption. Whether you are on a Classic or DPS license model, the measurement unit for metric ingestion is based on metric datapoints.
To estimate the amount of metric datapoints produced by your extension configuration, use the following list which gives you a number of metrics per feature set and a multiplier value depending on the number of connection pools being monitored. Add all of these up, and you will have the number of datapoints produced every minute.
Connection pool time XA: 9 x number of connection pools.Connection pool XA:5 x number of connection pools.Connection pool: 5 x number of connection pools.Connection pool time: 9 x number of connection pools.
For example, a monitoring configuration that contains one connection pool where all feature sets are activated produces 28 metric datapoints per minute.
By extrapolation, it will ingest:
28 x 60 x = 1,680metric datapoints per hour.28 x 60 x 24 = 40,320metric datapoints per day.28 x 60 x 24 x 365 = 14,716,800metric datapoints per year.
Since JMX Extensions run on OneAgent-monitored hosts, they are subjected to included metrics per host unit.
Please refer to the following documentation depending on the license type:
Troubleshooting
- To troubleshoot this extension, use the guide(s) in the Dynatrace Community.
Feature sets
When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.
Connection pool XA
| Metric name | Metric key | Description |
|---|---|---|
| Max pool size (XA) | jboss.connectionPool.maxPoolSizeXA | — |
| Active count (XA) | jboss.connectionPool.ActiveCountXA | — |
| Available count (XA) | jboss.connectionPool.AvailableCountXA | — |
| Created count (XA) | jboss.connectionPool.CreatedCountXA.count | — |
| Destroyed count (XA) | jboss.connectionPool.DestroyedCountXA.count | — |
| Idle count (XA) | jboss.connectionPool.IdleCountXA | — |
| In use count (XA) | jboss.connectionPool.InUseCountXA | — |
| Timed out (XA) | jboss.connectionPool.TimedOutXA.count | — |
| Wait count (XA) | jboss.connectionPool.WaitCountXA.count | — |
Connection pool
| Metric name | Metric key | Description |
|---|---|---|
| Max pool size | jboss.connectionPool.maxPoolSize | — |
| Active count | jboss.connectionPool.ActiveCount | — |
| Available count | jboss.connectionPool.AvailableCount | — |
| Created count | jboss.connectionPool.CreatedCount.count | — |
| Destroyed count | jboss.connectionPool.DestroyedCount.count | — |
| Idle count | jboss.connectionPool.IdleCount | — |
| In use count | jboss.connectionPool.InUseCount | — |
| Timed out | jboss.connectionPool.TimedOut.count | — |
| Wait count | jboss.connectionPool.WaitCount.count | — |
Connection pool time
| Metric name | Metric key | Description |
|---|---|---|
| Total blocking time | jboss.connectionPool.TotalBlockingTime.count | — |
| Total creation time | jboss.connectionPool.TotalCreationTime.count | — |
| Total pool time | jboss.connectionPool.TotalPoolTime.count | — |
| Total get time | jboss.connectionPool.TotalGetTime.count | — |
| Total usage time | jboss.connectionPool.TotalUsageTime.count | — |
Connection pool time XA
| Metric name | Metric key | Description |
|---|---|---|
| Total blocking time (XA) | jboss.connectionPool.TotalBlockingTimeXA.count | — |
| Total get time (XA) | jboss.connectionPool.TotalGetTimeXA.count | — |
| Total creation time (XA) | jboss.connectionPool.TotalCreationTimeXA.count | — |
| Total usage time (XA) | jboss.connectionPool.TotalUsageTimeXA.count | — |
| Total pool time (XA) | jboss.connectionPool.TotalPoolTimeXA.count | — |
