|
Measures reported by EgObjectPoolTest
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.
The measures
made by this test are as
follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Initial_connections |
Indicates the number of objects initially allocated to this pool. |
Number |
|
| Max_connections |
Indicates the maximum number of objects this pool can contain. |
Number |
| Used_connections |
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_connections |
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. |
| Connection_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_connections |
Indicates the total number of objects in this pool. |
Number |
|
|