SWS JVM Test
This test reports the overall health of the JVM of the web server instance being monitored by measuring the following:
- How well the JVM manages the memory heap;
- The level of activity on the JVM in terms of the number of threads that are currently in use;
Target of the test : An Oracle iPlanet Web Server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for the web server instance being monitored.
Parameter | Description |
---|---|
Test period |
How often should the test be executed. |
Host |
The host for which the test is to be configured. |
Port |
The port number at which the specified Host listens to. |
User |
Specify the name of the administrator of the administration server to which the target web server is registered. |
PasswdFile |
The eG agent connects to the administration server to which the target web server is registered to extract the required metrics. To enable the eG agent to communicate with this administration server, you first need to create a password file containing the administrator password for accessing the server; this password file should be created in the install directory of the web server. Specify the name of this file in the PasswdFile text box; by default, this is admin.passwd. |
AdminServer |
Specify the IP address of the administration server to which the target web server is registered. |
AdminPort |
Indicate the port at which the administration server listens. |
Config |
In Web Server 7.0, all configurable elements of a server instance like web applications, configuration files, and search collection indexes are logically grouped and termed as a Configuration. To enable the test to locate the web server instance to be monitored, you need to mention the Configuration that applies to the instance. In the Config text box therefore, specify the name of the Configuration which the target web server instance uses. |
Node |
Node is a network resource, such as a server or a host. Instance refers to the environment of a web server daemon on a given node, including its configuration, log files and other runtime artifacts such as lock databases, caches and temporary files. To enable the test to identify the exact web server instance to be monitored, you need to specify the name of the Node on which the instance executes. The test will thus monitor only that web server instance that operates on the given Node and which uses the specified Config. |
SSL |
Set this flag to Yes if the administration server is SSL-enabled; if not, set it to No. |
WebServerDir |
Here, specify the Oracle iPlanet web server installation directory. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Heap memory size |
Indicates the current heap memory size. |
MB |
|
Elapsed GC Time |
Indicates the time taken for garbage collection. |
Secs |
If adequate memory is not allotted to the JVM, then the value of this measure would be very high. This is not a good sign, as GC, during its execution, has the tendency of suspending an application, and a high value of this measure would only adversely impact the server’s performance. To avoid this, it is recommended that you allot sufficient memory to the JVM. |
No. of GC occurred |
Indicates the number of garbage collections that occurred during the last measurement period. |
Number |
If adequate memory is not allotted to the JVM, then the value of this measure would be very high. A high value of this measure is indicative of a high frequency of GC. This is not a good sign, as GC, during its execution, has the tendency of suspending an application, and a high frequency of GC would only adversely impact the server's performance. To avoid this, it is recommended that you allot sufficient memory to the JVM. |
Present classes loaded |
Indicates the number of classes currently loaded in the JVM. |
Number |
|
No of classes loaded |
Indicates the number of classes that were loaded during the last measurement period. |
Number |
|
No of classes unloaded |
Indicates the number of classes unloaded during the last measurement period. |
Number |
|
No of live threads |
Indicates the number of live daemon and non-daemon threads. |
Number |
A large number of threads is indicative of high JVM activity. |
No of started threads |
Indicates the number of threads created and/or started during last measurement period. |
Number |
|
Peak Live Thread Count |
Indicates the peak live thread count since the JVM started or the peak was reset. |
Number |
|