JMX properties aren't working anymore
search cancel

JMX properties aren't working anymore

book

Article ID: 191345

calendar_today

Updated On:

Products

CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management (APM / Wily / Introscope) INTROSCOPE DX Application Performance Management

Issue/Introduction

We upgraded our Weblogic domains from version 10.3.6 to 12.2.1.3 and the following JMX properties aren't working anymore (it worked in Weblogic version 10.3.6):
 

JDBCConnectionPoolRuntime:WaitingForConnectionCurrentCount
JDBCConnectionPoolRuntime:ConnectionsTotalCount
JDBCConnectionPoolRuntime:LeakedConnectionCount
JDBCConnectionPoolRuntime:ActiveConnectionsCurrentCount
 

We've already opened a service request at Oracle and they show us that the metric name is: JDBCDataSourceRuntime:
http://www.catgovind.com/weblogic/weblogic-jmx-api-example-how-to-monitor-weblogic-jdbc-data-source-using-java-jmx-jdbcdatasourceruntimembeans/
 

In addition, we are able to locate all of these metrics through JConsole (via JMX) but we still couldn't collect this information in Introscope.
 

We tried to adjust the filter in IntroscopeAgent.profile, leaving it blank. This way Introscope can find JDBC metrics, but we can't locate any of the metrics bellow:
 

ActiveConnectionsCurrentCount
LeakedConnectionCount
ConnectionsTotalCount
WaitingForConnectionCurrentCount

Environment

Release : 10.7.0

Component : APM Agents

Resolution

We identify the metric in JConsole and adjust it in the IntroscopeAgente.profile file:

The following filter setting should able to report the metrics in investigator.

introscope.agent.jmx.name.filter=JDBCDataSourceRuntime*:WaitingForConnectionCurrentCount, JDBCDataSourceRuntime*:ConnectionsTotalCount, JDBCDataSourceRuntime*:LeakedConnectionCount, JDBCDataSourceRuntime*:ActiveConnectionsCurrentCount