9.11.4 Defining and monitoring the number of requests pending for each URL group
You specify the definition for monitoring the number of requests pending for each URL group.
- Organization of this subsection
(1) Attribute file to be edited
WAR attribute file
(2) Acquiring the attribute file to be edited and setting the attributes
-
Acquiring the attribute file
Execute the following command to acquire a WAR attribute file:
- Execution format
cjgetappprop [server-name] [-nameserver provider-URL] -name J2EE application-name -type war -resname WAR-display-name -c path-of-the-WAR-attribute-file
- Example of execution
cjgetappprop MyServer -name adder -type war -resname adder_war -c C:\home\adder_war.xml
-
Setting the attributes
Execute the following command to apply the values of the WAR attribute file:
- Execution format
cjsetappprop [server-name] [-nameserver provider-URL] -name J2EE application-name -type war -resname WAR-display-name -c path-of-the-WAR-attribute-file
- Example of execution
cjsetappprop MyServer -name adder -type war -resname adder_war -c C:\home\adder_war.xml
(3) Attribute settings to be edited
The following table describes the property settings for monitoring the number of requests pending for each URL group (<urlgroup-thread-control> - <stats-monitor> - <waiting-request-count>):
|
Items |
Mandatory |
Corresponding tags |
|---|---|---|
|
Existence of threshold value event monitoring |
Y |
<enabled> |
|
Output upper threshold value of threshold value event# |
Y |
<high-threshold> |
|
Output lower threshold value of threshold value event# |
Y |
<low-threshold> |
- Legend:
-
Y: Mandatory
- #
-
Specify such that 'Upper threshold value that outputs the threshold value event ≥ Lower threshold value that outputs the threshold value event'.
For details on the property settings, see 3.7.1 Specifications of the HITACHI WAR Property file in the uCosminexus Application Server Application and Resource Definition Reference Guide.