9.11.2 Defining the control of the number of threads executed concurrently for each Web application
You specify the definition in order to control the number of threads executed concurrently in the Web container.
- 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 controlling the number of threads executed concurrently in the Web container (<thread-control>):
Items |
Mandatory |
Corresponding tags |
---|---|---|
Maximum number of threads executed concurrently |
Y |
<thread-control-max-threads> |
Number of exclusive threads |
Y |
<thread-control-exclusive-threads> |
Size of the pending queue of each Web application |
Y |
<thread-control-queue-size> |
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.