| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Create_count |
The number of times this EJB was created during the last measurement period |
Number
|
|
| Avg_create_time |
The average time taken by a bean create call |
Secs
|
Ideally, this value should be low. |
| Remove_count |
The number of times this bean was removed during the last measurement period |
Number
|
|
| Avg_remove_time |
The average time taken by a bean remove call |
Secs
|
|
| Activation_count |
The number of times this bean was activated during the last measurement period |
Number
|
|
| Avg_activation_time |
The average time taken by a bean activate call, including teh time at the database |
Secs
|
Ideally, this value should be low. |
| Passivate_count |
The number of times this bean was passivated during the last measurement period |
Number
|
|
| Avg_passivate_time |
The average time taken by a bean passivate call, including the time at the database |
Secs
|
|
| Load_count |
The number of times this bean was loaded from the persistent storage during the last measurement period |
Number
|
|
| Avg_load_time |
The average time for loading a bean data from the persistent storage |
Secs
|
Ideally, this value should be low. |
| Store_count |
The number of times this bean was stored in the persistent storage during the last measurement period |
Number
|
|
| Avg_store_time |
The average time for storing this bean in a persistent storage |
Secs
|
|
| Instantiates_count |
The number of times this bean was instantiated during the last measurement period |
Number
|
A sudden increase in tthe number of instantiations indicates a bottleneck on the server. It may be due to greater load on the server or there might be a loophole in the application. |
| Freed_count |
The number of times during the last measurement period this bean object was freed |
Number
|
A very low value indicates a bottleneck on the server. This might affect the performance of the application. |
| Ready_count |
The number of concurrently ready beans |
Number
|
Greater the ready beans count, better will be the application performance. |
| Passive_count |
The number of beans in the passivated state during the last measurement |
Number
|
|
| Pooled_count |
The number of objects currently in the pool |
Number
|
|
| Drains_count |
The number of times during the last measurement period the daemon found the pool was idle and attempted to clean it |
Number
|
|
| Retrieve_count |
The number of calls during the last measurement period retrieving an object from the pool |
Number
|
|
| Retrieve_success_count |
The number of times a retrieve found an object in the pool, during the last measurement period |
Number
|
|
| Returns_count |
The number of calls returning an object to the pool, during the last measurement period |
Number
|
|
| Returns_discard_count |
The number of times during the last measurement period the returning object was discarded because the pool was full |
Number
|
Ideally, this value should be low. A consistent high value could indicate a full pool, and consequently, an overloaded server. You might then want to consider resizing the pool in order to accomodate more number of objects. |
| Methods_call_count |
The number of method calls during the last measurement period |
Number
|
A high value indcates that the server is busy. |
| Methods_response_time |
The average response time of the bean methods |
Secs
|
This value should be low for optimal performance of the application server. The value may go high, if there are more objects in the pool, which is a sign of overload. |