This section explains the method of setting up the tuning parameters used for optimizing the number of concurrent executions.
This subsection explains how to set up the tuning parameters for the number of request-processing threads, when you use an in-process HTTP server.
Set up the items listed in the following table in the Easy Setup definition file. Afterward re-build the system using the Smart Composer functionality.
Table 8-6 Tuning parameters for the number of request-processing threads (to use an in-process HTTP server)
Setup item | Setup target | Location of setup (parameter name) |
---|---|---|
Number of request-processing threads generated when the J2EE server is started | Logical J2EE server (j2ee-server) | webserver.connector.inprocess_http.init_threads |
Upper limit of the number of connections with the Web client (upper limit of the number of request-processing threads) | Logical J2EE server (j2ee-server) | webserver.connector.inprocess_http.max_connections |
Maximum value of the Listen queue (back log) of TCP/IP, when the maximum number of connections with the Web client is exceeded | Logical J2EE server (j2ee-server) | webserver.connector.inprocess_http.backlog |
Maximum number of spare threads | Logical J2EE server (j2ee-server) | webserver.connector.inprocess_http.max_spare_threads |
Minimum number of spare threads | Logical J2EE server (j2ee-server) | webserver.connector.inprocess_http.min_spare_threads |
For details about the tuning parameters when you use Cosminexus HTTP Server during the Web server integration, see the uCosminexus Application Server HTTP Server User Guide.
Set in each URL group, Web application or Web container.
This subsection explains how to set up the tuning parameters for number of concurrent executions of a URL group. The method and location of the setup is different for each setup item.
You specify the items listed in the following table using the Smart Composer functionality. You define the parameters in the Easy Setup definition file.
Table 8-7 Tuning parameters of the number of concurrent executions of a URL group (items to be specified using the Smart Composer functionality)
Setup item | Setup target | Location of setup (parameter name) |
---|---|---|
Maximum number of concurrently executed threads in each Web container (during the Web server integration) | Logical J2EE server (j2ee-server) | webserver.connector.ajp13.max_threads |
Maximum number of concurrently executed threads in each Web container (when using an in-process HTTP server) | Logical J2EE server (j2ee-server) | webserver.connector.inprocess_http.max_execute_threads |
Whether to control the number of concurrent executions for each Web application | Logical J2EE server (j2ee-server) | webserver.container.thread_control.enabled |
Default pending queue size | Logical J2EE server (j2ee-server) | webserver.container.thread_control.queue_size |
You specify the items listed in the following table using the server management command (cjsetappprop). You define parameters in the WAR property file.
Table 8-8 Tuning parameters of the number of concurrent executions of a URL group (items to be specified using the server management command (cjsetappprop))
Setup item | Location of setup (parameter name) |
---|---|
Maximum number of concurrently executed threads in each Web application | <thread-control-max-threads> under <thread-control> tag |
Number of dedicated threads of the Web application | <thread-control-exclusive-threads> under <thread-control> tag |
Pending queue size of the Web application | <thread-control-queue-size> under <thread-control> tag |
Definition the name of concurrently executed thread control for a URL group | <urlgroup-thread-control-name> under <thread-control> <urlgroup-thread-control> tag |
Maximum number of concurrently executed threads in a URL group | <urlgroup-thread-control-max-threads> under <thread-control> <urlgroup-thread-control> tag |
Number of dedicated threads in a URL group | <urlgroup-thread-control-exclusive-threads> under <thread-control> <urlgroup-thread-control> tag |
Pending queue size of a URL group | <urlgroup-thread-control-queue-size> under <thread-control> <urlgroup-thread-control> tag |
URL pattern to be controlled for each URL group | <urlgroup-thread-control-mapping> under <thread-control> <urlgroup-thread-control> tag |
This subsection explains how to set up the tuning parameters for the number of concurrent executions in each Web application. The method and location of setup is different for each setup item.
You specify the items listed in the following table using the Smart Composer functionality. You define the parameters in the Easy Setup definition file.
Table 8-9 Tuning parameters of the number of concurrent executions in a Web application (items to be specified using the Smart Composer functionality)
Setup item | Setup Target | Location of setup (parameter name) |
---|---|---|
Maximum number of concurrently executed threads in each Web container (during the Web server integration) | Logical J2EE server (j2ee-server) | webserver.connector.ajp13.max_threads |
Maximum number of concurrently executed threads in each Web container (when using an in-process HTTP server) | Logical J2EE server (j2ee-server) | webserver.connector.inprocess_http.max_execute_threads |
Whether to control the number of concurrent executions for each Web application | Logical J2EE server (j2ee-server) | webserver.container.thread_control.enabled |
Default pending queue size | Logical J2EE server (j2ee-server) | webserver.container.thread_control.queue_size |
You specify the items listed in the following table using the server management command (cjsetappprop). You define the parameters in the WAR property file.
Table 8-10 Tuning parameters of the number of concurrent executions in the Web application (items to be specified using the server management command (cjsetappprop))
Setup item | Location of setup (parameter name) |
---|---|
Maximum number of concurrently executed threads in each Web application | <thread-control-max-threads> |
Number of dedicated threads of a Web application | <thread-control-exclusive-threads> |
Pending queue size for each Web application | <thread-control-queue-size> |
This subsection explains how to set up the tuning parameters for the number of concurrent executions in each Web container.
You specify the items listed in the following table using the Smart Composer functionality. You define the parameters in the Easy Setup definition file.
Table 8-11 Tuning parameter of the number of concurrent executions in a Web container
Setup item | Setup target | Location of setup (parameter name) |
---|---|---|
Maximum number of concurrently executed threads in each Web container (during the Web server integration) | Logical J2EE server (j2ee-server) | webserver.connector.ajp13.max_threads |
Maximum number of concurrently executed threads in each Web container (when using an in-process HTTP server) | Logical J2EE server (j2ee-server) | webserver.connector.inprocess_http.max_execute_threads |
The number of concurrent executions of an Enterprise Bean is set for each Enterprise Bean. The settings are explained below for each type of Enterprise Bean:
This subsection explains how to set up the tuning parameters for the number of concurrent executions of a Stateless Session Bean.
You specify the items listed in the following table using the server management command (cjsetappprop). You define the parameters in the Session Bean property file.
Table 8-12 Tuning parameters of the number of concurrent executions of the Stateless Session Bean
Setup item | Location of setup (parameter name) |
---|---|
Maximum number of instances managed in the pool | <maximum> under <stateless> <pooled-instance> tag# |
Minimum number of instances managed in the pool | <minimum> under <stateless> <pooled-instance> tag |
This subsection explains how to set up the tuning parameters for the number of concurrent executions of a Stateful Session Bean.
You specify the items listed in the following table using the server management command (cjsetappprop). You define the parameters in the Session Bean property file.
Table 8-13 Tuning parameters of the number of concurrent executions of a Stateful Session Bean
Setup item | Location of setup (parameter name) |
---|---|
Maximum number of sessions that can be generated from the client | <maximum-active-sessions> under <stateful> tag |
Time (minutes) until the unused instances are deleted | <removal-timeout> under <stateful> tag |
This subsection describes how to set up the tuning parameters for the number of concurrent executions of an Entity Bean.
You specify the items listed in the following table using the server management command (cjsetappprop). You define the parameters in the Entity Bean property file.
Table 8-14 Tuning parameters of the number of concurrent executions of an Entity Bean
Setup item | Location of setup (parameter name) |
---|---|
Maximum value of the Entity Bean that can be generated from the client | <maximum-instances> |
Time (minutes) until the EJBObject of the unused Entity Bean is deleted | <entity-timeout> |
This subsection describes how to set up the tuning parameters for the number of concurrent executions of a Message-driven Bean.
You specify the items listed in the following table using the server management command (cjsetappprop), and define the parameters in the Message-driven Bean property file.
Table 8-15 Tuning parameters of the number of concurrent executions of a Message-driven Bean
Setup item | Location of setup (parameter name) |
---|---|
Maximum number of instances managed in the pool | <pooled-instance> <maximum> |
Minimum number of instances managed in the pool | <pooled-instance> <minimum> |
This subsection describes how to set up the tuning parameters for the number of concurrent executions controlled with CTM. The items are set up in CTM daemon, application, and Stateless Session Bean.
Set up the items listed in the following table in the Easy Setup definition file. Afterward re-build the system using the Smart Composer functionality.
Table 8-16 Tuning parameter for the number of concurrent executions controlled with CTM (item to be specified using the Smart Composer functionality)
Setup item | Setup target | Location of setup (parameter name) |
---|---|---|
Maximum value of threads controlled with CTM, and number of requests registered in each queue | Logical CTM (component-transaction-monitor) | ctm.DispatchParallelCount |
Set up the items listed in the following table using the server management commands. Define the parameters in the application property file or Session Bean property file.
Table 8-17 Tuning parameters for the number of concurrent executions controlled with CTM (items to be specified using the server management commands)
Setup item | Definition file | Setup target | Location of setup (parameter name) |
---|---|---|---|
Whether to control the number of concurrent executions with CTM in the application | Application property file | Application | <managed-by-ctm> |
Number of concurrently executed threads of the application | Application property file | Application | parallel-count below the <scheduling> tag |
Whether to control the number of concurrent executions with CTM in the Stateless Session Bean | Session Bean property file | Stateless Session Bean | <enable-scheduling> |
Settings for the queues of each Bean# | Session Bean property file | Stateless Session Bean | parallel-count below the <scheduling> tag |