Connection Pools: WebLogicConnection Pools: WebLogic
Application server method of pooling and sharing connections to a database.
Extension
- Product information
- Release notes
Overview
Several built-in 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 Oracle Weblogic.
Prerequisites:
- Oracle Weblogic 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 Oracle Weblogic 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 Weblogic Connection Pool Overview dashboard.
Extension content
Content typeNumber of items included
metric query
1
screen injections
2
screen metric tables
1
generic relationship
1
metric metadata
16
dashboards
1
screen layout
1
screen chart groups
3
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 feature sets can be activated and deactivated by your administrator during configuration.
Feature setsNumber of metrics included
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Statement cache size | weblogic.connectionPool.prepStmtCacheCurrentSize | - | Count |
| Statement cache hits | weblogic.connectionPool.prepStmtCacheHitCount.count | - | Count |
| Statement cache misses | weblogic.connectionPool.prepStmtCacheMissCount.count | - | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Stuck thread count | weblogic.stuckThreads | - | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Active connections | weblogic.connectionPool.activeConnectionsCurrentCount | - | Count |
| Current capacity | weblogic.connectionPool.currCapacity | - | Count |
| Leaked connections | weblogic.connectionPool.leakedConnectionCount.count | - | Count |
| Available connections (idle) | weblogic.connectionPool.numAvailable | - | Count |
| Waiting for connections | weblogic.connectionPool.waitingForConnectionCurrentCount | - | Count |
| Failed connection requests | weblogic.connectionPool.failedReserveRequestCount.count | - | Count |
| Reconnection failures | weblogic.connectionPool.failuresToReconnectCount.count | - | Count |
| Requests for connections | weblogic.connectionPool.reserveRequestCount.count | - | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Current message count | weblogic.currentMessages | - | Count |
| Pending message count | weblogic.pendingMessages | - | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Max capacity | weblogic.connectionPool.maxCapacity | - | Count |
Full version history
To have more information on how to install the downloaded package, please follow the instructions on this page.
ReleaseDate
Full version history
Added three new metrics:
- weblogic.currentMessages
- weblogic.pendingMessages
- weblogic.stuckThreads
Full version history
- Fixed a bug were some metrics were counted as monotonic even if they were not. This fix changes the metric key for:
- weblogic.connectionPool.currCapacity.count -> weblogic.connectionPool.currCapacity
- weblogic.connectionPool.numAvailable.count -> weblogic.connectionPool.numAvailable
- weblogic.connectionPool.waitingForConnectionCurrentCount.count -> weblogic.connectionPool.waitingForConnectionCurrentCount
- weblogic.connectionPool.prepStmtCacheCurrentSize.count -> weblogic.connectionPool.prepStmtCacheCurrentSize
Full version history
- Fixed a bug where func:weblogic.connectionPool.currentUsage was still not being populated
Full version history
Fixed a bug with metric keys that solves:
- Metrics not showing on the overview dashboard
- Metrics not showing up on the unified analysis screens
- Metrics not having any metadata
- The metric func:weblogic.connectionPool.currentUsage not being populated
Full version history
EF1 to EF2 Weblogic Connection Pool conversion:
- Add Weblogic connection pool entity and its relation to the weblogic process
- Custom unified analysis screen for Weblogic connection pools
- Metric chart injection into Process Group Instance screen
- Overview dashboard for Weblogic connection pools
- Add feature sets to control included metrics
- New metric func:weblogic.connectionPool.currentUsage that shows the current connection usage
- All metrics have changed key from the EF1 version. The prefix builtin:tech.weblogic has been removed. This is a breaking change for any configuration you had which used the metric key, such as metric events.