This
test periodically tracks the measures related to the Java virtual machine of
all the instances of a JRun server. The measures reported by this test are as given hereunder:
| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Total_serv_memory
|
This value indicates the total amount of memory that is being
currently used by the server. |
MB
|
An unusually large usage of memory by the server is a cause for
concern. Further analysis is required to determine whether any of the
applications running have memory leaks. If the memory is still low,
consider starting the server with a higher memory usage setting.
|
| Free_serv_memory
|
This value indicates the total amount of memory that is not in use by
the server. |
MB
|
A very low value of free memory is also an indication of high memory
utilization within the JVM.
|
| Num_active_sessions
|
This indicates the current number of active sessions in the server. |
Number
|
A high value of this measure may indicate an increase in the server
workload.
|
| Num_mem_sessions
|
This indicates the number of active sessions in the server memory.
Sessions can be persisted to a session repository depending upon your
JRun configuration. |
Number
|
A high value may indicate that there are a large number of sessions
residing in the memory. Some of these sessions might be active or
inactive. If the value is too high, consider changing the value of session.persistence
to false. This would stop persistence of a session when the server is
terminated.
|
| Note:
If a new server instance is added to a JRun application server
while its being monitored, it will take at least an hour for the new
instance to appear in the eG monitor console. |