B.1 Tuning parameters for specifying the timeout (methods other than the recommended procedures)
This appendix describes the locations to set up the tuning parameters used for specifying the timeout.
- Organization of this subsection
-
-
(2) Timeout specified in the redirector for sending data to the Web container
-
(3) Timeout specified in the redirector for receiving data from the Web container
-
(4) Timeout specified in the Web container for receiving data from the redirector
-
(5) Timeout specified in the Web container for receiving data from the redirector
-
(7) Timeout set up in the EJB client for invoking the Enterprise Bean from CTM
-
(8) Timeout specified in the EJB container for the database transaction (when DB Connector is used)
(1) Timeout specified in the Web server for receiving requests from the client and sending data to the client
For the Web server integration, set up the tuning parameter for each Web server. As for the in-process HTTP server, set up the parameters in every J2EE server.
Web server to be used |
Method of setup |
Location of setup |
---|---|---|
Web server integration |
Management portal (For Cosminexus HTTP Server) |
Timeout directive of "Additional directives" of "Perform the setup for each item" in "Web Server Setup" window. |
Timeout directive of "Setup file details" of "Directly set the details of setup file" in "Web Server Setup" window. |
||
Edit file# |
|
|
In-process HTTP server |
Edit file |
webserver.connector.inprocess_http.receive_timeout key in usrconf.properties |
webserver.connector.inprocess_http.send_timeout key in usrconf.properties |
- #
-
Set up the tuning parameters by editing httpd.conf, a definition file of Cosminexus HTTP Server.
(2) Timeout specified in the redirector for sending data to the Web container
The following table describes the tuning parameters for the timeout to be specified in the redirector. You can specify these tuning parameters only for the Web server integration.
Web server type |
Method of setup |
Location of setup |
---|---|---|
Cosminexus HTTP Server |
Edit file |
JkConnectTimeout parameter of mod_jk.conf |
Microsoft IIS |
Edit file |
connect_timeout key in isapi_redirect.conf |
Cosminexus HTTP Server |
Edit file |
JkSendTimeout parameter of mod_jk.conf |
Microsoft IIS |
Edit file |
send_timeout key in isapi_redirect.conf |
(3) Timeout specified in the redirector for receiving data from the Web container
Set up the tuning parameters for each worker definition of the redirector. The following table describes the methods and locations to set up the tuning parameters for the timeout to be specified in the redirector:
Method of setup |
Location of setup |
---|---|
Edit file |
worker.worker-name.receive_timeout key in workers.properties |
You can specify this tuning parameter only for the Web server integration.
(4) Timeout specified in the Web container for receiving data from the redirector
Set up the tuning parameter for each J2EE server. The following table describes the tuning parameters for the timeout to be specified in the Web container:
Method of setup |
Location of setup |
---|---|
Edit file |
webserver.connector.ajp13.receive_timeout key in usrconf.properties |
You can specify this tuning parameter only for the Web server integration.
(5) Timeout specified in the Web container for receiving data from the redirector
Set up the tuning parameter for each J2EE server. The following table describes the tuning parameters for the timeout to be specified in the Web container:
Method of setup |
Location of setup |
---|---|
Edit file |
webserver.connector.ajp13.send_timeout key in usrconf.properties |
You can specify this tuning parameter only for Web server integration.
(6) Timeout specified in the EJB client for remotely invoking the Enterprise Bean (RMI-IIOP communication) and for invoking the Naming Service by JNDI
Set up 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 the timeout to be specified in the EJB client:
Unit |
Method of setup |
Location of setup |
---|---|---|
Each J2EE server |
Edit file |
ejbserver.rmi.request.timeout key in usrconf.properties |
The setup of the tuning parameter for each EJB client application and for each API is the same as specified for the recommended procedures.
The following table describes the tuning parameters (Naming Service invocation) for the timeout to be specified in the EJB client:
Unit |
Method of setup |
Location of setup |
---|---|---|
Each J2EE server |
Edit file |
ejbserver.jndi.request.timeout key in usrconf.properties |
The setup of the tuning parameters for each EJB client application is the same as specified in the recommended procedures.
(7) Timeout set up in the EJB client for invoking the Enterprise Bean from CTM
Set up the tuning parameter in J2EE server unit, EJB client application unit, or invocation API unit.
The same value as that specified in (6) Timeout specified in the EJB client for remotely invoking the Enterprise Bean (RMI-IIOP communication) and for invoking the Naming Service by JNDI is inherited as the setup value of this timeout.
(8) Timeout specified in the EJB container for the database transaction (when DB Connector is used)
Set up the tuning parameter for each J2EE server, Enterprise Bean, interface, method (for CMT), or each invocation by API (for BMT).
The following table describes the tuning parameters for the transaction timeout:
Unit |
Method of setup |
Location of setup |
---|---|---|
Each J2EE server |
Edit file |
ejbserver.jta.TransactionManager.defaultTimeOut key in usrconf.properties |
The setup of the tuning parameters for the Enterprise Bean, interface, each method (for case of CMT), and API (for BMT) are the same as specified in the recommended procedures.
(9) Database timeout
The setup of the tuning parameter specified for the database timeout are the same as that specified in the recommended procedures.