2.2.9 Setting the timeout

This subsection describes the procedure for setting the following timeouts:

Method timeout of J2EE applications
Communication timeout for response awaiting data
Default transaction timeout period for a transaction
Database timeout (For HiRDB)

Reference note

For details on the reference locations of the windows, commands, and files used in the description, and the storage locations of the commands and files, see 5. Windows, Commands, and Files used in the System Setup and Operations.

Organization of this subsection

(1) Setting the method timeout for J2EE application
(2) Setting communication timeout for response awaiting data
(3) Default settings for transaction timeout period of transaction
(4) Response timeout and request interval timeout settings (for HiRDB)

(1) Setting the method timeout for J2EE application

Use the execution time monitoring functionality of J2EE applications for setting the request processing waiting period in Web container.

Edit cosminexus.xml and store in the META-INF directory under Any directory.

Specify following in the <war> tag of cosminexus.xml.
- Specify the value of the J2EE application method timeout in <servlet>-<method-observation-timeout> tag.
If there are multiple <servlet> tags within <war> tag, specify the values in the respective tags.
Execute jar command with the command prompt, and set the cosminexus.xml edited in step 1, in J2EE application of archive format.

The command execution example is as follows:
```
jar uvf <MyApp1.ear file path> -C Directory where META-INF directory is placed <cosminexus.xml file path under META-INF directory>
```
Specify the path of the directory that stores J2EE application (MyApp1.ear), and the file name (MyApp1.ear) in MyAppl.ear file path. The <Directory where META-INF directory is placed> is Any directory, if the structure of the store destination of cosminexus.xml is as follows.
```
<Any directory>
 - META-INF
 - cosminexus.xml
```
Specify the path of META-INF directory where the cosminexus.xml is stored in step 1 and the file name (cosminexus.xml) in <cosminexus.xml file path under META-INF directory>.

To Page Top

(2) Setting communication timeout for response awaiting data

Set how long the reverse proxy registered in the Web server waits to receive data from the Web container.

Start the Web browser, connect to http://localhost:28080/mngsvr/index.jsp, and start the management portal.
Enter "admin" for the management user ID in the Login Management Server window and click the Login button.
Click Logical server environment settings in the Management Portal window.
On the Server view tab, select DefaultDomain, Logical Web server, Web server, and MyWebServer, and then click the Reverse proxy tab.
Enter the desired value in Communication timeout in the Setting the Reverse Proxy window, and then click the Apply button.

A message indicating the saving of environment settings appears.
Click the Deploy the Settings anchor.
Click the Deploy All button on the Deploy the Settings window.

The Status changes from "Blank" to "Deploying", and then to "Deployed".

Reference note

If there are logical servers having the Status as "Deployed", you can select and deploy only the logical servers having the status as "Blank". In such cases, insert check mark in Deploy, and then click the Select and Deploy button. The Status of the selected logical server changes to "Deployed".
Click Start/Stop the Logical Server on the Management Portal window.
In the Server view tab, Click DefaultDomain and then click the Batch Restart tab.
Click the Execute button in the Batch Restart window.

The request for a batch restart is received and the operational status of logical servers in the Operational Status of Logical Servers window successively changes from "Operating" to "Stopping", to "Stopped" then to "Starting" and then to "Operating".

To Page Top

(3) Default settings for transaction timeout period of transaction

Set the transaction timeout for the EJB container and the database.

Start the Web browser, connect to http://localhost:28080/mngsvr/index.jsp, and start the Management Portal.
Enter "admin" for the management user ID in the Login Management Server window and click the Login button.
Click Logical Server Environment Settings in the Management Portal window.
In the Server View tab, select DefaultDomain - Logical J2EE Server - J2EE Server - MyJ2EEServer and then click the Services - Transaction tab.
Set a value in the Timeout period in the Transaction Settings window and click the Apply button.

A message indicating the saving of the environment settings appears.
Click the Deploy the Settings anchor.
Click the Deploy All button in the Deploy the Settings window.

The Status changes from "Blank" to "Deploying", and then to "Deployed".

Reference note

If there are logical servers having the Status as Deployed, you can select and deploy only the logical servers having the status as Blank. In such cases, check Deploy and then click the Select and Deploy button. The Status of the selected logical server changes to "Deployed".
Click Start/Stop the Logical Server in the Management Portal window.
In the Server View tab, click DefaultDomain and then click the Batch Restart tab.
Click the Execute button in the Batch Restart window.

The request for a batch restart is received and the operational status of the logical servers in the Operational Status of Logical Servers window sequentially changes from "Operating" to "Stopping", to "Stopped", then to "Starting", and then to "Operating".

To Page Top

(4) Response timeout and request interval timeout settings (for HiRDB)

Set the timeout (response timeout) for detecting failures on the server side of the database system, and the timeout (request interval timeout) for detecting failures on the client side of the database system.

Start the Web browser, connect to http://localhost:28080/mngsvr/index.jsp, and start the Management Portal.
Enter "admin" for the management user ID in the Login Management Server window and click the Login button.
Click Application Management of the Logical Server on the Management Portal window.
Click DefaultDomain - Logical J2EE server - J2EE server - MyJ2EEServer - Resources - Resource adapter, and then click the Start/Stop tab.
Click the Stop anchor of Operation, if the Status on the Start/Stop Resource Adapter window is "Operating".
Click the Yes button on the Stop Resource Adapter window.
Click the Back anchor if "Success" is displayed in the Execution result.

If "Failure" is displayed in the Execution result, click the Display log tab, check the message in the Display Log window, remove the cause of failure and then stop the resource adapter again.
Click DefaultDomain - Logical J2EE Server - J2EE Server - MyJ2EEServer - Resources - Resource Adapter, and then click the Property Settings tab.
Click the Basic settings anchor of Operation in the Resource Adapter Property Settings window.
Set PDCWAITTIME and PDSWAITTIME values in HiRDB client environment variable (environmentVariables) in the Basic Settings of the Resource Adapter window and click the Settings button.

You can set the response timeout (PDCWAITTIME) and request interval timeout (PDSWAITTIME).
Check the message displayed in the Basic Settings of Resource Adapter window, and click the Back anchor.

If a failure message is displayed, remove the cause of failure and then set the property again.
Click the Back anchor.
Click the Start/Stop tab and then click the Start anchor of Operation in the Start/Stop Resource Adapter window.
Click the Yes button on the Start Resource Adapter window.
Click the Back anchor if "Success" is displayed in the Execution result.

If "Failure" is displayed in the Execution result, click the Display log tab, check the message in the Display Log window, remove the cause of failure, and then start the resource adapter again.

To Page Top