Confirm the operational status of a running Web application. You can confirm the operational status of a Web application using the management command (mngsvrutil) . After confirming the operational status, consider whether to change the maximum number of concurrently executing threads in cases such as described below:

• When the number of pending threads is too large in number as compared to the number of active threads in a situation when this condition is not assumed
• When the current value of the number of pending requests of a Web application is approaching the maximum value of the number of pending requests of the Web application, in the case when this condition is not assumed
• When requests are overflowing from the pending queue of the Web application, in a situation when this condition is not assumed
  When you monitor and determine that it is necessary to change the maximum number of concurrently executing threads permanently, rather than changing dynamically stop the Web application and reset the maximum number of concurrently executing threads. For details on the settings for controlling the maximum number of concurrently executing threads in the Web container when the Web application is not running, see 2.16 Controlling the number of concurrently executing threads in the Web Container, 2.17 Controlling the number of concurrently executing threads in the Web application, and 2.18 Controlling the number of concurrently executing threads in the URL group.
  

To check the operational status of the Web application, specify and execute subcommand get in the mngsvrutil command.

The execution format and an example are described below. For details on the mngsvrutil command, see mngsvrutil (Management command of Management Server) in the uCosminexus Application Server Command Reference Guide.

Execution format

mngsvrutil -m Management-Server-host-name [:port-number] -u Management-user-ID -p Management-password -t host-name -k host get webApps

Execution example

mngsvrutil -m mnghost -u user01 -p pw1 -t host01 -k host get webApps
 

The execution result of the command is output in a standard output or file.

From the statistics of a running Web application, you can check the information to be referred when changing the maximum number of concurrently executing threads of a Web application with the following header information items. Note that N seconds is the sampling time that is set by management.

Table 2-61 Information to be referred when changing the maximum number of concurrently executing threads of a Web application

Header information	Contents
contextRoot	Context root of a Web application
exclusiveThreadCountUpperBound	Number of dedicated threads of a Web application
activeThreadCountUpperBound	Maximum number of concurrently executing threads of a Web application
waitingRequestCountUpperBound	Pending queue size of a Web application
currentThreadCountUpperBound	Upper value of the number of threads of a Web application that can be executed concurrently
activeThreadCount	Current value of the number of active threads
activeThreadCountPeak	N seconds peak of the number of active threads
activeThreadCountAverage	N seconds average value of the number of active threads
activeThreadCountHightWaterMark	Maximum value of the number of active threads
activeThreadCountLowWaterMark	Minimum value of the number of active threads
waitingRequestCount	Current value of the number of pending requests of a Web application
waitingRequestCountPeak	N seconds peak of the number of pending requests of a Web application
waitingRequestCountAverage	N seconds average value of the number of pending requests of a Web application
waitingRequestCountHighWaterMark	Maximum value of the number of pending requests of a Web application
waitingRequestCountLowWaterMark	Minimum value of the number of pending requests of a Web application
overflowRequestCount	Number of requests overflowing from the pending queue of a Web application

Change the following items of a Web application, the operational status of which is confirmed, as required:

• Maximum number of concurrently executing threads
• Number of dedicated threads
• Size of a pending queue

You can change these items with management command (mngsvrutil) . The value set here is applied until the Web application stops.

Note

Do not deploy and undeploy a J2EE application when dynamically changing (when the sub command change is specified in the mngsvrutil command) the maximum number of concurrently executing threads of a Web application.

For dynamically changing the maximum number of concurrently executing threads of a Web application, specify and execute the sub command change in the mngsvrutil command.

The following is the execution format. For details on the mngsvrutil command, see mngsvrutil (Management command of Management Server) in the uCosminexus Application Server Command Reference Guide.

Execution format

mngsvrutil -m Host-name-of-Management-Server [:port-number] -u Management-user-ID -p Management-password -t host-name -k host change webAppThreadCtrl Context-root-of-the-Web-application Maximum-number-of-concurrently-executing-threads, number-of-dedicated-threads, pending-queue-size-of-Web-application

The following is an execution example. In this example, the settings are changed as shown in the following table. Note that the name of the Web application is WebAP1.

Table 2-62 Example of settings for dynamically changing the maximum number of concurrently executing threads of a Web application (WebAP1)

Setting target	Settings	Setting before change	Setting after change
Web container	Maximum number of concurrently executing threads	10	10 (cannot be changed)
Web application (WebAP1)	Maximum number of concurrently executing threads	7	8
	Number of dedicated threads	4	5
	Size of a pending queue	8	10

Execution example

mngsvrutil -m mnghost -u user01 -p pw1 -t host01 -k host change webAppThreadCtrl "WebAP1" 8, 5, 10

The set contents are applied immediately after executing the command.