This subsection describes the methods and locations for setting up the tuning parameters used to optimize the number of concurrent executions.
The following table describes the methods and locations to set up the tuning parameters for the number of request-processing threads, when an in-process HTTP server is used:
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.19,22,59
Table C-1 Tuning parameters for the number of request-processing threads when an in-process HTTP server is used (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.inprocess_http.init_threads key in usrconf.properties |
Upper-limit of the number of connections to the Web client (upper-limit of the number of request-processing threads) | Edit file | webserver.connector.inprocess_http.max_connections key in usrconf.properties |
Maximum value of the Listen queue (back log) of TCP/IP, when the maximum number of connections to the Web client exceeds | Edit file | webserver.connector.inprocess_http.backlog key in usrconf.properties |
Maximum number of spare threads | Edit file | webserver.connector.inprocess_http.max_spare_threads key in usrconf.properties |
Minimum number of spare threads | Edit file | webserver.connector.inprocess_http.min_spare_threads key in usrconf.properties |
Setup for each URL group, Web application, or Web container.
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 (during the Web server integration) | Edit file | webserver.connector.ajp13.max_threads key in usrconf.properties |
Maximum number of concurrently executed threads in each Web container (for using an in-process HTTP server) | Edit file | webserver.connector.inprocess_http.max_execute_threads key in usrconf.properties |
Whether to control the number of concurrent executions for each Web application | Edit file | webserver.container.thread_control.enabled key in usrconf.properties |
Whether to control the number of concurrent executions for each Web application | 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:
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 each Web container (during the Web server integration) | Edit file | webserver.connector.ajp13.max_threads key in usrconf.properties |
Maximum number of concurrently executed threads in Web container unit (for using an in-process HTTP server) | Edit file | webserver.connector.inprocess_http.max_execute_threads key in usrconf.properties |
Whether to control the number of concurrent executions for each Web application | Edit file | webserver.container.thread_control.enabled 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:
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 (during the Web server integration) | Edit file | webserver.connector.ajp13.max_threads key in usrconf.properties |
Maximum number of concurrently executed threads in each Web container (for using an in-process HTTP server) | Edit file | webserver.connector.inprocess_http.max_execute_threads key in usrconf.properties |
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.
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.