JRun Server Test

This test periodically tracks the measures related to the Java virtual machine of all the instances of a JRun server.

Target of the test : An Allaire JRun Server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for the JRun Server being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.


Specify the host name of the server for which the test is to be configured.


The port number on which the host is listening.


The directory in which the JRun server has been installed.

In Windows environments, if the JRun server is installed at D:\program files\allaire\jrun, HomeDir has to be set to D:\progra~1\allaire\jrun.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Total server memory

This value indicates the total amount of memory that is being currently used by the server.


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 server memory

This value indicates the total amount of memory that is not in use by the server.


A very low value of free memory is also an indication of high memory utilization within the JVM.

Active sessions

This indicates the current number of active sessions in the server.


A high value of this measure may indicate an increase in the server workload.

Sessions in memory

This indicates the number of active sessions in the server memory. Sessions can be persisted to a session repository depending upon your JRun configuration.


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.


If a new server instance is added to a JRun application server while its being monitored, it will take at least hour for the new instance to appear in the eG monitor console.