JRun Service Test

This test monitors the processing of requests by 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.

Host

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

Port

The port number on which the host is listening.

HomeDir

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

Avg queue time

This value indicates the average time a request spends waiting for processing by the server.

Secs

A low value here would indicate that the server is performing optimally. An increase in queuing delay reflects a server bottleneck. For a JRun server 3.0, consider increasing the jcp.endpoint.main.active.threads property in the local.properties file, to ensure that additional threads are available to process incoming requests.

In case of a JRun server 4.0, modify the activeHandlerThreads attribute of the WebService in the jrun.xml file located in the <JRUN_HOME_DIR>/servers/<SERVER_NAME>/SERVER-INF directory.

A number of compute intensive tasks can also end up increasing the queuing time for a request.

Avg processing time

This value indicates the average time taken by the server to process a request.

Secs

A high value here would indicate that processing time per request is very high, as the requests might be performing complex/time-consuming computation. Consider determining which of the server side processing tasks is compute intensive and explore ways of minimizing the server processing overhead.

Avg response time

This indicates the average time spent by a request in queuing and processing.

Secs

An increase in response time can occur because there are too many simultaneous requests or because of a bottleneck with any of the applications executing on the server.

Data read rate

This indicates the total rate of data received by the server for all incoming requests.

KB/Sec

An unusually high value indicates an increase in workload to the server. The Avg queue time metric indicates whether the increased incoming data rate is impacting the server performance.

Data write rate

This indicates the total rate of data sent by the server in response to all incoming requests.

KB/Sec

An unusually high value indicates an increase in workload to the server. The Avg queue time metric indicates whether the increased incoming data rate is impacting the server performance.

Delayed requests

This value  indicates the number of requests delayed at the server.

Number

While the Avg queue time gives an indicator of how long requests are being queued, this measure provides an indicator of how many requests were queued at the server over the last measurement period. This value should be close to 0 for peak performance.

Dropped requests

This indicates the number of requests that were dropped since the server could not process them or queue them.

Number

This value should be close to 0 at most times. Therefore, if a JRun server 3.0 drops a large number of requests, consider increasing the parameter jcp.endpoint.main.max.threads, in the local.properties file. This parameter indicates the maximum number of requests that can be processed or queued at any instant.

In case of a JRun server 4.0, modify the activeHandlerThreads attribute of the WebService in the jrun.xml file located in the <JRUN_HOME_DIR>/servers/<SERVER_NAME>/SERVER-INF directory.

Request rate

This indicates the rate of requests handled by the JRun server.

Reqs/sec

This value is an indicator of server workload across all its connectors.

Note:

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.