C.1 Tuning parameter for optimizing the number of concurrent executions (methods other than the recommended procedures)

This subsection describes the methods and locations for setting up the tuning parameters used to optimize the number of concurrent executions.

Organization of this subsection

(1) Number of request-processing threads when using an NIO HTTP server
(2) Number of concurrent executions in a Web application
(3) Number of concurrent executions in an Enterprise Bean
(4) Number of concurrent executions controlled by CTM

(1) Number of request-processing threads when using an NIO HTTP server

The following table describes the methods and locations to set up the tuning parameters for the number of request-processing threads when using an NIO HTTP server.

For details about the tuning parameters when Cosminexus HTTP Server is used for Web server integration, see the uCosminexus Application Server HTTP Server User Guide.

Table C‒1: Tuning parameters for the number of request-processing threads when using an NIO HTTP (methods other than the recommended procedures)
Setup item	Method of setup	Location of setup
Number of request-processing threads generated when the J2EE server is started	Edit file	`webserver.connector.nio_http.min_threads` key in `usrconf.properties`
Maximum number of connections to the Web client or reverse proxy	Edit file	`webserver.connector.nio_http.max_connections` key in `usrconf.properties`
Maximum value (backlog) of the TCP/IP Listen queue used when the maximum number of connections to the Web client or reverse proxy is exceeded	Edit file	`webserver.connector.nio_http.backlog` key in `usrconf.properties`
Maximum number of request-processing threads	Edit file	`webserver.connector.nio_http.max_threads` key in `usrconf.properties`

To Page Top

(2) Number of concurrent executions in a Web application

Setup for each URL group, Web application, or Web container.

(a) Number of concurrent executions for a URL group

The following table describes the methods and locations to set up the tuning parameters for the number of concurrent executions of a URL group:

Table C‒2: Tuning parameters for the number of concurrent executions of a URL group (methods other than the recommended procedures)
Setup item	Method of setup	Location of setup
Maximum number of concurrently executed threads in each Web container	Edit file	`webserver.connector.nio_http.max_servlet_execute_threads` key in `usrconf.properties`
Default pending queue size	Edit file	`webserver.container.thread_control.queue_size` key in `usrconf.properties`

The following setup items are the same as specified for the recommended procedures:

Maximum number of concurrently executed threads in each Web application
Number of dedicated threads for the Web application
Size of the pending queue in a Web application
Definition name of concurrently executed thread control of a URL group
Maximum number of concurrently executed threads in a URL group
Number of dedicated threads for a URL group
Size of the pending queue in a URL group
URL pattern to be controlled by a URL group

(b) Number of concurrent executions for a Web application

The following table describes the methods and locations to set up the tuning parameters for the number of concurrent executions in a Web application:

Table C‒3: Tuning parameters for the number of concurrent executions in a Web application (methods other than the recommended procedures)
Setup item	Method of setup	Location of setup
Maximum number of concurrently executed threads in Web container unit	Edit file	`webserver.connector.nio_http.max_servlet_execute_threads` key in `usrconf.properties`
Default pending queue size	Edit file	`webserver.container.thread_control.queue_size` key in `usrconf.properties`

The following setup items are the same as specified for the recommended procedures:

Maximum number of concurrently executed threads in each Web application
Number of dedicated threads of the Web application
Size of the pending queue in a Web application

(c) Number of concurrent executions for a Web container

The following table describes the methods and locations to set up the tuning parameters for the number of concurrent executions in a Web container:

Table C‒4: Tuning parameters for the number of concurrent executions in a Web container (methods other than the recommended procedures)
Setup item	Method of setup	Location of setup
Maximum number of concurrently executed threads in each Web container	Edit file	`webserver.connector.nio_http.max_servlet_execute_threads` key in `usrconf.properties`

To Page Top

(3) Number of concurrent executions in an Enterprise Bean

Set up the number of concurrent executions in an Enterprise Bean for each Enterprise Bean.

The tuning parameters for the number of concurrent executions in an Enterprise Bean are the same as specified for the recommended procedures.

To Page Top

(4) Number of concurrent executions controlled by CTM

The following table describes the methods and locations to set up the tuning parameters for the number of concurrent executions controlled by CTM. The items are set up in the CTM daemon, application, and Stateless Session Bean.

The following table describes the methods and locations to set up the tuning parameters for the number of concurrent executions controlled by CTM:

Table C‒5: Tuning parameters for the number of concurrent executions controlled by CTM (methods other than the recommended procedures)
Setup target	Setup item	Method of setup	Location of setup
CTM daemon	Maximum value of threads controlled by CTM, and number of requests registered in each queue	Edit file	Argument `-CTMDispatchParallelCount` of the `ctmstart` command

The setup items of the application or Stateless Session Bean are the same as specified in the recommended procedures.

To Page Top