Consider a data source whose Inactive Connection Timeout has been set to 60 seconds. You suspect that an application is not returning JDBC connections to this data source. In response, you go to the data source’s Monitoring tab in the Administration Console. Which of the available columns will confirm your suspicious?

The Leaked Connection Count is a specific monitoring metric in WebLogic Server designed to identify and count connections that have been checked out by an application but not returned to the pool within a configured time limit. When an application fails to close a JDBC connection, WebLogic's leak detection mechanism flags it. An incrementing value in this column is a direct confirmation that the application is leaking connections, which aligns perfectly with the suspicion described in the scenario.

A. State: This indicates the overall operational status of the data source (e.g., Running, Suspended), not the status of individual connections being used by applications.
B. Active Connections Current Count: This shows how many connections are currently in use. While a high or constantly increasing count is a symptom of a leak, it is not definitive proof, as it could also represent legitimate high load.
C. Connection Delay Time: This measures the wait time for a connection when the pool is exhausted. It is a consequence of having no available connections, which a leak can cause, but it does not directly confirm the leak itself.
E. Current Capacity: This shows the total number of physical database connections currently in the connection pool, including both active and available connections. It does not differentiate between properly used and leaked connections.

1. Oracle WebLogic Server Documentation 12.2.1.4.0

"Administering JDBC Data Sources for Oracle WebLogic Server":

Section: "Monitoring Data Source Statistics" -> "Monitoring Statistics for a JDBC Data Source"

Content: The table describing monitoring statistics explicitly defines Leaked Connection Count as "The number of leaked connections. A leaked connection is a connection that was reserved from the data source but was not returned to the data source by calling close()." This directly supports option D as the confirmation metric. It also defines Active Connections Current Count as "The number of connections currently in use by applications

" confirming it is an indicator but not a direct confirmation of a leak.

2. Oracle WebLogic Server Documentation 12.2.1.4.0

"Oracle WebLogic Server Administration Console Online Help":

Section: "JDBC Data Source: Monitoring: Statistics"

Content: This page in the console help provides definitions for all available columns on the monitoring tab. The definition for Leaked Connection Count confirms it is the specific metric for tracking connections that were not properly closed and returned to the pool. This source validates that this is the correct column to check in the Administration Console.