Skip to technology filters Skip to main content
Dynatrace Hub

Extend the platform,
empower your team.

Popular searches:
Home hero bg
Connection Pools: WebLogicConnection Pools: WebLogic
Connection Pools: WebLogic

Connection Pools: WebLogic

Application server method of pooling and sharing connections to a database.

Extension
Free trial
Monitor all your connection pools for Weblogic closely by analyzing their data directly on the Unified Analysis screen for each connection pool individually.
  • 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:

  1. Install OneAgent on the virtual machine or server of your Oracle Weblogic process.
  2. Activate the OneAgent feature Java Metric Extensions 2.0 (JMX).
  3. Select in this same tile Add to environment to configure the extension.
  4. Open the Weblogic Connection Pool Overview dashboard.
Dynatrace
More Information
By Dynatrace
Dynatrace support center
Subscribe to new releases
Copy to clipboard

Extension content

Content typeNumber of items included
screen injections
2
metric query
1
screen metric tables
1
generic relationship
1
dashboards
1
screen layout
1
screen chart groups
3
list screen layout
1
metric metadata
17
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 nameMetric keyDescriptionUnit
Max capacityweblogic.connectionPool.maxCapacity-Count
Metric nameMetric keyDescriptionUnit
Current message countweblogic.currentMessages-Count
Pending message countweblogic.pendingMessages-Count
Metric nameMetric keyDescriptionUnit
Active connectionsweblogic.connectionPool.activeConnectionsCurrentCount-Count
Current capacityweblogic.connectionPool.currCapacity-Count
Leaked connectionsweblogic.connectionPool.leakedConnectionCount.count-Count
Available connections (idle)weblogic.connectionPool.numAvailable-Count
Waiting for connectionsweblogic.connectionPool.waitingForConnectionCurrentCount-Count
Failed connection requestsweblogic.connectionPool.failedReserveRequestCount.count-Count
Reconnection failuresweblogic.connectionPool.failuresToReconnectCount.count-Count
Requests for connectionsweblogic.connectionPool.reserveRequestCount.count-Count
Metric nameMetric keyDescriptionUnit
Stuck thread countweblogic.stuckThreads-Count
Hogging thread countweblogic.hoggingThreads-Count
Metric nameMetric keyDescriptionUnit
Statement cache sizeweblogic.connectionPool.prepStmtCacheCurrentSize-Count
Statement cache hitsweblogic.connectionPool.prepStmtCacheHitCount.count-Count
Statement cache missesweblogic.connectionPool.prepStmtCacheMissCount.count-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

Fixed a bug where these new metrics were not being captured correctly:

  • weblogic.currentMessages
  • weblogic.pendingMessages
  • weblogic.stuckThreads

Added a new metric:

  • weblogic.hoggingThreads

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.
Dynatrace Hub
Hub HomeGet data into DynatraceBuild your own app
Log Management and AnalyticsKubernetesAI and LLM ObservabilityInfrastructure ObservabilitySoftware DeliveryApplication ObservabilityApplication SecurityDigital ExperienceBusiness Analytics
Filter
Type
Built and maintained by
Deployment model
SaaS
  • SaaS
  • Managed
Partner FinderBecome a partnerDynatrace Developer

All

1 Results filtered by:

Akamas logo

Akamas

Enabling enterprises to maximize service quality, resilience and cost savings.