Specify the maximum and minimum threshold values and issue an event when the number of pending requests in a URL group reaches the respective threshold value. The event of maximum threshold value and the event of minimum threshold value are issued at the timing mentioned below. The maximum threshold value needs to be greater than the minimum threshold value.
• A maximum threshold value event is issued when the number of pending requests in a URL group reaches the maximum threshold value (warning zone).
• A minimum threshold value event is issued to indicate that normal state is restored, when the number of pending requests in a URL group reaches the minimum threshold value after a maximum threshold value event was issued. • A maximum threshold value event is issued when the maximum threshold value is reached once again after the
number of pending requests in a URL group has fallen below the minimum threshold value once after the maximum threshold value event was issued. A maximum threshold value event is not issued when the maximum threshold value is reached again without reaching the minimum threshold value, after the maximum threshold value event was issued.
• A minimum threshold value event is issued when the minimum threshold value is reached again after the number of pending requests in a URL group exceeds the maximum threshold value since a minimum threshold value event was issued. A minimum threshold value event is not issued when the minimum threshold value is reached again without reaching the maximum threshold value, after the minimum threshold value event is issued.
The following figure illustrates the issuing of a threshold value event when the number of pending requests in a URL group is used:
Figure 3‒4: Issuing of a threshold value event (when the number of pending requests in a URL group is used)
In the above figure, a maximum threshold value event is issued when the threshold value reaches the maximum value from the normal zone. Next, the maximum threshold value is reached once again after falling below the maximum threshold value, but a maximum threshold value event is not issued at this time. From this point onwards, a minimum threshold value event is issued when the minimum threshold value is reached and a maximum threshold value event is issued when the maximum threshold value is reached.
3.4.3 Definition in cosminexus.xml
This subsection describes definition of cosminexus.xml required in the application development environment. Specify the definition for using the event issuing functionality in the <war> tag of cosminexus.xml.
The following table describes the definition of the event issuing functionality in cosminexus.xml: Table 3‒24: Definition of the event issuing functionality in cosminexus.xml
Monitoring target Tags to be specified Setting contents
Number of entire pending requests for Web applications
<thread-control>-<thread-control- stats-monitor>-<whole-waiting- request-count>-<enabled>
Specify whether to enable the monitoring of the entire pending request count of a Web application. The default value is true.
<thread-control>-<thread-control- stats-monitor>-<whole-waiting- request-count>-<high-threshold>
Specify the upper limit threshold value of the entire pending request count for a Web application. The value is specified with the percentage (%) stored for the number of entire pending requests for Web applications.
<thread-control>-<thread-control- stats-monitor>-<whole-waiting- request-count>-<low-threshold>
Specify the lower limit threshold value of the entire pending request count for a Web application. The value is specified with the percentage (%) stored for the number of entire pending requests for Web applications.
Number of pending requests for Web applications
<thread-control>-<thread-control- stats-monitor>-<waiting-request- count>-<enabled>
Specify whether to enable the monitoring of the pending request count of a Web application. The default value is true.
<thread-control>-<thread-control- stats-monitor>-<waiting-request- count>-<high-threshold>
Specify the upper limit threshold value for the pending request count for a Web application. The value is specified with the percentage (%) stored for the number of pending requests for Web
applications.
<thread-control>-<thread-control- stats-monitor>-<waiting-request- count>-<low-threshold>
Specify the lower limit threshold value of the pending request count for a Web application. The value is specified with the percentage (%) stored for
Monitoring target Tags to be specified Setting contents Number of pending
requests for Web applications
<thread-control>-<thread-control- stats-monitor>-<waiting-request- count>-<low-threshold>
the number of pending requests for Web applications.
Number of pending requests for URL groups
<thread-control>-<urlgroup-thread- control>-<stats-monitor>-<waiting- request-count>-<enabled>
Specify whether to enable the monitoring of the pending request count of the URL group. The default value is true.
<thread-control>-<urlgroup-thread- control>-<stats-monitor>-<waiting- request-count>-<high-threshold>
Specify the upper limit threshold value for the pending request count for a URL group. The value is specified with the percentage (%) stored for the number of pending requests for URL groups.
<thread-control>-<urlgroup-thread- control>-<stats-monitor>-<waiting- request-count>-<low-threshold>
Specify the lower limit threshold value for the pending request count for a URL group. The value is specified with the percentage (%) stored for the number of pending requests for URL groups. For details on the tags to be specified, see 2.2.6 War property details in the uCosminexus Application Server Application and Resource Definition Reference Guide.
3.4.4 Settings for the execution environment (J2EE server settings)
To issue events using the statistics file, you must specify the J2EE server and J2EE application settings. You reference the J2EE application settings only when you want to set or change the properties of a J2EE application that does not contain cosminexus.xml.
(1) Setting J2EE servers
Implement the J2EE server settings in the Easy Setup definition file. Specify the definition for issuing events of the <configuration> tag for the logical J2EE server (j2ee-server), in the Easy Setup definition file.
The following table describes the definition for event issuing specified in the Easy Setup definition file. Table 3‒25: Definition for event issuing in the Easy Setup definition file
Parameters to be specified Setting contents
ejbserver.management.JVM.stats_monitor.FullGC Count.enabled
Specify whether to enable the monitoring of the full garbage collection frequency. The default value is true.
ejbserver.management.JVM.stats_monitor.FullGC Count.threshold
Specify the threshold value for monitoring the full garbage collection frequency.
ejbserver.management.JVM.stats_monitor.FullGC Count.interval
Specify the threshold value interval for monitoring the full garbage collection frequency.
ejbserver.management.webcontainer.stats_monit or.whole_waiting_request_count.enabled
Specify whether to enable the monitoring of the entire pending request count of a Web container. The default value is true.
ejbserver.management.webcontainer.stats_monit or.whole_waiting_request_count.high_threshold
Specify the upper limit threshold value of the entire pending request count for a Web container.
ejbserver.management.webcontainer.stats_monit or.whole_waiting_request_count.low_threshold
Specify the lower limit threshold value of the entire pending request count for a Web container.
ejbserver.management.webcontainer.stats_monit or.waiting_request_count.enabled
Specify whether to enable the monitoring of the pending request count of a Web container. The default value is true.
ejbserver.management.webcontainer.stats_monit or.waiting_request_count.high_threshold
Specify the upper limit threshold value of the pending request count for a Web container.
ejbserver.management.webcontainer.stats_monit or.waiting_request_count.low_threshold
Specify the lower limit threshold value of the pending request count for a Web container.
For details on the Easy Setup definition file and the parameters to be specified, see 4.6 Easy Setup definition file in the
uCosminexus Application Server Definition Reference Guide.
(2) Setting J2EE applications
You implement the J2EE application settings for the execution environment using the server management commands and the property files. You use the WAR property file to define the issuing of events.
The tags specified in the WAR property file correspond to cosminexus.xml. For details on the definitions of