Anda di halaman 1dari 2

Página 1 de 2

AS Console Shows more Connections in the Database than Configured for the Datasource [ID
414478.1]

Modified 27-JUL-2009 Type PROBLEM Status MODERATED

In this Document
Symptoms
Cause
Solution

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

Applies to:

Enterprise Manager for iAS - Version: 10.1.2.0.2


This problem can occur on any platform.

Symptoms

AS Console JDBC metrics are not consistent with actual opened connections in the database.

After some tests V$SESSION shows 1 open connection, which was open from a data-source using pooling while AS Console JDBC usage report 3 opened connections.

Settings for the data-source regarding pool of connections was : min-connections=1 max-connections=2

Metrics referenced are the ones displayed when an OC4J is select from the list of AS components:

"Open JDBC Connections" and "Total JDBC Connections"

Cause

In this case it was actually not a problem, but misunderstanding about meaning of the metrics.

Solution

By checking the on-line help provided with the AS Console, the definitions for the JDBC metrics above are:

Open JDBC Connections defined as:


"Displays the number of open JDBC connections by applications that are part of this OC4J instance. "

Total JDBC Connections defined as:


" Displays the number of total JDBC connections created by applications that are part of this OC4J
instance."

Open JDBC Connections ==> this is the number of current connections open.
This metric should match current sessions shown by v$session.

Please be advised that the v$session view in the DB shows all connections to the DB, and it is needed to isolate from v$session

how many of the connections originated from a particular data-source from a particular oc4j container.

Total JDBC Connections ==>


" Displays the number of total JDBC connections created by applications that are part of this OC4J instance."
This metric shows an accumulative value of "created connections" since last start-up of the JVM.

Please consider the following hypothetical scenarios to better understand the metrics above.
Data-source pool parameters:
min-connections= 2
max-connections=4

Scenario 1. all 4 connections were created and kept used/active during the morning.
so:
Open JDBC Connections=4
Total JDBC Connections=4.

Scenario 2. imagine 30 minutes of inactivity of the application at lunch time.


This causes data-source pool to physically return/close two connections, so it goes back to min-connections open/active.
so:
Open JDBC Connections=2
Total JDBC Connections=4

Scenario 3. afternoon shift starts and users actively use the application, which requires the all 4 connections be active again.
There were 2 already open connections (min-connections), but two additional connections needs to be created
so:
Open JDBC Connections=4
Total JDBC Connections=6

Note: metrics in EM console are updated with some delay, so connections created and/or dropped are shown after several seconds delay.

Related

Products

• Enterprise Management > Enterprise Manager Consoles, Packs, and Plugins > Managing Middleware using Enterprise Manager > Enterprise Manager for iAS

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=PROBLE... 10/29/2010
Página 2 de 2

Keywords

DATASOURCE; METRIC; V$SESSION

Back to top

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=PROBLE... 10/29/2010

Anda mungkin juga menyukai