eG Object Pools Test

The eG manager uses four object pools to manage database connections of each of the modules it supports. These object pools are as follows - DB Adapter Admin, DB Adapter Monitor, DB Adapter Config, and DB Adapter Reporter. If any of these pools run out of objects, then the eG manager will not be able to establish database connections and will eventually crash! To make sure that all the object pools are adequately sized, use this test and track the usage of each object pool, isolate the pools that do not have sufficient objects, and resize them.

Target of the test : The eG Manager

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for each object pool of the eG manager.

Configurable parameters for the test
Parameter	Description
Test period	How often should the test be executed .
Host	The host for which the test is to be configured.
Port	The port number at which the specified host listens.
JMX Remote Port	Here, specify the port at which the JMX listens for requests from remote hosts. In the <EG_MANAGER_INSTALL_DIR>\manager directory (on Windows; on Unix, this will be the /opt/egurkha/manager directory) of the eG manager, you will find a management.properties file. Set the port defined against the com.sun.management.jmxremote.port parameter of the file as the JMX Remote Port.
User, Password, and Confirm Password	By default, JMX requires no authentication or security. Therefore, the User, Password , and Confirm Password parameters are set to none by default.
JNDIName	The JNDIName is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have registered the JMX connector in the RMI registry using a different lookup name, then you can change this default value to reflect the same.
JMX Provider	This test uses a JMX Provider to access the MBean attributes of the eG manager and collect metrics. Specify the package name of this JMX Provider here. By default, this is set to com.sun.jmx.remote.protocol.
Timeout	Specify the duration (in seconds) for which this test should wait for a response from the eG manager. If there is no response from the eG manager beyond the configured duration, the test will timeout. By default, this is set to 240 seconds.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Initial objects	Indicates the number of objects initially allocated to this pool.	Number
Maximum objects	Indicates the maximum number of objects this pool can contain.	Number
Used objects	Indicates the objects that are currently used in this pool.	Number	If the value of this measure grows dangerously close to the value of the Maximum objects measure, it indicates that the pool is rapidly running out of objects.
Free objects	Indicates the number of unused objects in this pool.	Number	A low value for this measure is a cause for concern, as it indicates that the object pool does not have enough free objects. This could be owing to an increase in the number of components monitored or the number of users accessing the systems. You may hence want to consider resizing the pool, so that the availability of the eG manager is not affected by the lack of adequate objects.
Object timeout	Indicates the time taken by the object to timeout.	Secs	By carefully observing the value for this measure over time, you can figure out the maximum ideal time for which an object should stay alive.
Total objects	Indicates the total number of objects in this pool.	Number