CLM Server Monitoring - Pool Monitor (DEPRECATED: CLM Server Monitoring is no longer supported and was dropped in version 6.0.3.)

The Pool monitor is responsible for gathering performance information of the different pools used by CLM applications. There are currently two types of object pools: "RDB mediator pool" and "JDBC connection pool". These pools are backed by a semaphore which is also monitored.

JMX Interface Name: com.ibm.team.server.monitoring.management.MonitorRollupMBean
JMX Object Name: team.server.<application public URI context>@<port>:type=Pool
JMX Object Name Example: team.server./jts@9443:type=Pool

A JMX object of this "type" will be created for each kind of pool:

• Pool Monitor JMX Object Name: team.server.<application public URI context>@<port>:type=Pool
  
• Pool Type JMX Object Name: team.server.<application public URI context>@<port>:type=Pool,name="(JDBC connection pool | RDB mediator pool)"
  

Statistical information is gathered pertaining to pool semaphore, in addition to the general statistics pertaining to the objects allocated therein.

In the case of the "JDBC connection pool", database connection objects are also captured as child MBeans, following the structure:

• Pool object JMX Object Name: team.server.<application public URI context>@<port>:type=Pool,name="JDBC connection pool",connectionname="<DBconnectionString>",id="<poolObjectID>"
  

Visually, the Pool Monitor objects structure would look like the following:

   team.server./<URL>@<port>:type=Pool
          |
          |
          |---- team.server./<URL>@<port>:type=Pool,name="JDBC connection pool"
          |                     |
          |                     |
          |                     | --- team.server./<URL>@<port>:type=Pool,name="JDBC connection pool",connectionname="jdbc:<JDBCconnectionChain>",id="<objectID>"
          |                     | ...
          |
          |---- team.server./<URL>@<port>:type=Pool,name="RDB mediator pool"   

Monitor Attributes

Following are the attributes exposed by the Pool Monitor.

Monitor Operations

Child MBeans

This section gathers information regarding MBeans that are contained within this monitor. The section is divided in the two different types of pools existing today: JDBC connection and RDB mediator

JDBC connection pool

JMX Interface Name: com.ibm.team.server.monitoring.jmx.beans.JDBCPoolMBean
JMX Object Name: team.server.<application public URI context>@<port>:type=Pool,name="JDBC connection pool"

Attributes

Note the attributes related with time statistics are expressed in miliseconds.

Each connection object in the pool it is itself monitored using a child MBean. The structure of these objects and information gathered is introduced next.

Child MBeans: JDBC connections

JDBC connection objects in the pool are monitored. One JMX object gets registered for each connection object in the pool.

JMX Interface Name: com.ibm.team.server.monitoring.jmx.beans.DBConnectionMBean
JMX Object Name: team.server.<application public URI context>@<port>:type=Pool,connectionname="<JDBCconnectionString>,id=<ID>
JMX Object Name Example: team.server./qm@9443:type=Pool,name="JDBC connection pool",connectionname="jdbc:derby:conf/qm/derby/repositoryDB",id=03cd63f5-a8c1-49e9-827d-f9d50568864e

Attributes

RDB mediator pool

A monitor for the RDB mediator pool

JMX Interface Name: com.ibm.team.server.monitoring.jmx.beans.JDBCPoolMBean
JMX Object Name: team.server.<application public URI context>@<port>:type=Pool,name="JDBC connection pool"

Attributes

Semaphore Stats information

The following table describes the Semaphore Stats information:

External links:

• IBM

Additional contributors: TWikiUser, TWikiUser