This section explains how to set up tuning parameters used for timeout settings.
This is a tuning parameter for setting the timeout at point 1 of Figure 8-9 or Figure 8-10. The location of setup differs according to the Web server used.
In the case of Web server integration, set the tuning parameter for each Web server. You edit the files for specifying the settings.
Table 8-27 Tuning parameters for the timeout to be set in the Web server for receiving requests from the client and sending the data to the client (for Web server integration)
Setup item | Location of setup |
---|---|
Timeout for receiving requests from the client and sending data to the client | Timeout directive of httpsd.conf |
Note: When you are using Microsoft IIS as the Web server, edit the receive_client_timeout key in isapi_redirect.conf.
For an in-process HTTP server, specify the settings in each J2EE server.
You set up the items listed in the following table using the Smart Composer functionality. Define the parameters in the Easy Setup definition file.
Table 8-28 Tuning parameters for the timeout to be set in the Web server for receiving requests from the client and sending the data to the client (for an in-process HTTP server)
Setup item | Setup target | Location of setup (parameter name) |
---|---|---|
Timeout for receiving requests from the client | Logical J2EE server (j2ee-server) | webserver.connector.inprocess_http.receive_timeout |
Timeout for sending data to the client | Logical J2EE server (j2ee-server) | webserver.connector.inprocess_http.send_timeout |
This is a tuning parameter for setting the timeout at point 2 and point 3 of Figure 8-9.The following table describes the tuning parameters for the timeout to be set in the redirector. You can specify the tuning parameter only in the case of Web server integration.
Specify the items listed in the following table with the Smart Composer functionality. You define the parameters in the Easy Setup definition file.
Table 8-29 Tuning parameters for the timeout to be set in the redirector
Point | Setup item | Setup target | Location of setup (parameter name)# |
---|---|---|---|
2 | Connection timeout for Web container when sending requests | Logical Web server (web-server) | JkConnectTimeout |
3 | Timeout for sending requests | Logical Web server (web-server) | JkSendTimeout |
This is a tuning parameter for setting the timeout at point 4 of Figure 8-9.
You set up the tuning parameters for each worker definition of the redirector. The following table describes the tuning parameters for the timeout to be set up in the redirector.
You specify the items listed in the following table using the Smart Composer functionality and define the parameters in the Easy Setup definition file.
Table 8-30 Tuning parameters for the timeout to be set in the redirector
Setup item | Setup target | Location of setup (parameter name) |
---|---|---|
Communication timeout of waiting for response data | Logical Web server (web-server) | worker.worker-name.receive_timeout |
You can specify this tuning parameter only in the case of Web server integration.
This is a tuning parameter for setting the timeout at point 5 of Figure 8-9.
You set up the tuning parameter for each J2EE server. The following table describes tuning parameters for the timeout to be set in the Web container.
You specify the items listed in the following table using the Smart Composer functionality and define the parameters in the Easy Setup definition file.
Table 8-31 Tuning parameters for the timeout to be set in the Web container
Setup item | Setup target | Location of setup (parameter name) |
---|---|---|
Timeout in waiting for reply from redirector | Logical J2EE server (j2ee-server) | webserver.connector.ajp13.receive_timeout |
You can specify this tuning parameter only in the case of Web server integration.
This is a tuning parameter for setting the timeout at the point 13 of Figure 8-9.
You set up the tuning parameter for each J2EE server. The following table describes the tuning parameters for the timeout to be set up in the Web container.
You specify the items listed in the following table using the Smart Composer functionality and define the parameters in the Easy Setup definition file.
Table 8-32 Tuning parameters for the timeout to be set in the Web container
Setup item | Setup target | Parameter name |
---|---|---|
Timeout of response sending process | Logical J2EE server (j2ee-server) | webserver.connector.ajp13.send_timeout |
You can specify this tuning parameter only in the case of Web server integration.
This is a tuning parameter for setting the timeout at point 7 of Figure 8-9 or Figure 8-10.
Set the tuning parameter for each J2EE server, EJB client application, or invocation by API.
The following table describes the tuning parameters (remote invocation by RMI-IIOP communication) for timeout to be set in the EJB client:
Table 8-33 Tuning parameters for the timeout to be set in the EJB client (remote invocation by RMI-IIOP communication)
Units | Method of setup | Setup item | Location of setup |
---|---|---|---|
Each J2EE server | Smart Composer functionality | Communication timeout between client and server |
|
Each EJB client application | Specify the system property to be specified at the time of editing or starting a file |
| |
Each API | API |
|
The following table describes the tuning parameters (invoking the Naming Service) for timeout to be set in the EJB client:
Table 8-34 Tuning parameters for the timeout to be set in the EJB client (invoking the Naming Service)
Units | Method of setup | Setup item | Location of setup |
---|---|---|---|
Each J2EE server | Smart Composer functionality | Period of communication timeout with Naming Service |
|
Each EJB client application | Specify the system property to be specified at the time of editing or starting a file |
|
This is a tuning parameter for setting up timeout at point 8 of Figure 8-9 or Figure 8-10.
You set up the tuning parameter for each J2EE server, EJB client application, or each invocation by API.
A value same as that set up in (6) Timeout set in the EJB client for remotely invoking Enterprise Bean (RMI-IIOP communication) and for invoking Naming Service by JNDI is inherited as the setup value of this timeout.
This is a tuning parameter for setting the timeout at point 10 of Figure 8-9 or Figure 8-10.
Set the tuning parameter for each J2EE server, Enterprise Bean, interface, method (in the case of CMT), or each invocation by API (in the case of BMT).
The following table describes the tuning parameters for transaction timeout:
Table 8-35 Tuning parameters for transaction timeout
Units | Method of setup | Setup item | Location of setup |
---|---|---|---|
Each J2EE server | Smart Composer functionality | Default transaction timeout value of a transaction |
|
Each Enterprise Bean, interface, method (in the case of CMT) | The cjsetappprop command of the server management command | Transaction timeout time |
|
Each API (in the case of BMT) | API | UserTransaction#setTransactionTimeout method# |
This is a tuning parameter for setting the timeout at point 11 of Figure 8-9 or Figure 8-10.
Set the tuning parameter for each DB Connector.
The following table describes the tuning parameters for DB Connector.
Table 8-36 Tuning parameters for DB Connector
Units | Method of setup | Setup item | Location of setup |
---|---|---|---|
Each DB Connector | Server management commands cjsetrarprop or cjsetresprop | Timeout in establishing a physical connection |
|
Timeout in the request for connection during connection depletion |
| ||
Each J2EE server | Smart Composer functionality | Timeout in detecting a connection error |
|
This is a tuning parameter for setting the timeout at point 12 of Figure 8-9 or Figure 8-10.
The database timeout differs according to the type of database used and the operation mode of the server. This section explains how to set the timeout value when accessing the HiRDB, Oracle, SQL Server, or XDM/RD E2 by using the DB Connector.
Set the timeout value in the common system definition of the HiRDB server or the environment variable of the HiRDB client. For details, see the manual HiRDB System Definition or the manual HiRDB UAP Development Guide.
The following table describes the tuning parameters used for setting the timeout in HiRDB:
Table 8-37 Tuning parameters for setting the timeout in HiRDB
Type of timeout | Location of setup | Method of setup (parameter name) | Settings |
---|---|---|---|
Unlock waiting timeout | Common system definition of the HiRDB server | pd_lck_wait_timeout parameter | The settings are optional. |
Response timeout | Environment variable of the HiRDB client | PDCWAITTIME | Specify a value greater than the value of transaction timeout. |
Request interval timeout | Environment variable of the HiRDB client | PDSWAITTIME | Specify a value greater than the value of transaction timeout. |
Set the timeout value in the DISTRIBUTED_LOCK_TIMEOUT parameter of the Oracle server definition.
In addition to the above, the setting of SesTm parameter of XAOpenString affects the timeout. This parameter cannot be tuned.
Set the timeout value by executing the parameter or statement in the environment settings option of the SQL Server.
The following table describes the tuning parameters for setting the timeout in the SQL Server.
Table 8-38 Tuning parameters for setting the timeout in the SQL Server
Type of timeout | Location of setup | Method of setup (name of parameter or statement | Settings |
---|---|---|---|
Timeout in acquiring memory | Server configuration option | query wait parameter | The settings are optional. |
Unlock waiting timeout | -- | SET LOCK_TIMEOUT statement | The settings are optional. |
Set the timeout value in the system option definition of the XDM/BASE, the environment variable of the HiRDB client, and the control statement for invoking control space or the control statement for invoking server space of the DB connection server.
The following table describes the tuning parameters for setting the timeout in XDM/RD E2:
Table 8-39 Tuning parameters for setting the timeout in XDM/RD E2
Type of timeout | Location of setup | Method of setup (parameter name) | Settings |
---|---|---|---|
Unlock waiting timeout | System option definition of XDM/BASE | TIMER | The settings are optional.#1 |
CPU timeout during SQL execution | The control statement for invoking control space or control statement for invoking server space of the DB connection server | SQLCTIME | Specify a value greater than the value of transaction timeout.#2 |
SQL execution timeout | The control statement for invoking control space or control statement for invoking server space of the DB connection server | SQLETIME | Specify a value greater than the value of transaction timeout.#2 |
Transaction timeout | The control statement for invoking control space or control statement for invoking server space of the DB connection server | SVETIME | Specify a value greater than the value of transaction timeout.#2 |
Response timeout | HiRDB client environment variable | PDCWAITTIME | Specify a value greater than the value of transaction timeout.#3 |
This is a tuning parameter for setting the timeout at point 6 and point 9 of Figure 8-9 or Figure 8-10.
Set the timeout value as an application attribute when you want to set the timeout for each method in the Web application or the Enterprise Bean. Set the operations in the case of timeout as an application attribute as well. You specify these items using the server management command (cjsetappprop).
The following table describes the tuning parameters for setting the timeout in the method execution time. The location of setup differs for each point.
Table 8-40 Tuning parameters for setting the timeout for the method execution time
Points to set | Type of timeout and operations in the case of timeout | Location of setup |
---|---|---|
6 | Request processing method for the filter, servlet or JSP |
|
9 | Request processing method for the Enterprise Bean |
|
6 and 9 | Operations for each application when timeout occurs |
|