9.3.1 Points where you can set up a timeout

In the systems for executing batch applications, you can set up timeouts at the points shown in the following figure:

Figure 9-1 Points where a timeout can be set up

[Figure]

The timeout specified at each point has a specific use that is described in the table below:

Table 9-2 Purpose of the timeout set up at each point and the default timeout settings

PointType of timeoutPrimary usage
1Timeout set up in the batch server for remotely invoking the Enterprise Bean (RMI-IIOP communication) and for invoking the JNDI Naming ServiceDetecting failures in the business processing (such as infinite loop and deadlocks) of the batch server or the communication path
2#Timeout set up in the batch server for invoking the Enterprise Bean from CTMDetecting failures in the business processing (such as infinite loop and deadlocks) of the batch server or the communication path
3Timeout set up for the method execution time in the EJB that accesses the Enterprise Bean through invocationDetecting failures in the business processing (such as infinite loop and deadlock) of the J2EE server
4Timeout set up in the batch server for the database transactionDetecting failures in database server (such as, server is down or a deadlock has occurred) or preventing the extended exclusive use of resources
5Database timeoutDetecting failures in database server (such as server is down or a deadlock has occurred) or preventing the extended exclusive use of resources
#
This point exists only when you are using CTM. For a configuration in which CTM is not used, the range of point 2 extends from the time of execution of remote invocation of the EJB from the batch server to the EJB container, until the dispatch of execution result from the EJB container to the batch server.

The basic guidelines for setting up the above timeouts are as follows:

Points 1 to 5 can be divided into following two categories depending on their location in the system:

For details about the settings for each point, see 9.3.3 Tuning parameters for setting up the timeout for the batch application execution platform and 8.6.8 Tuning parameters for setting the timeout for the J2EE application execution platform.

Reference note
The default value of each point is as follows:
PointDefault value
1Not set up. Continues to wait for a response.
2A value same as point 1 is automatically inherited and set up when the Enterprise Bean is invoked.
3Not set up. A timeout does not occur.
4180 seconds
5Differs according to the type of the database and the location of setup of the timeout#
For HiRDB
Unlock waiting timeout: 180 seconds
Response timeout: 0 seconds (The HiRDB client continues to wait until a response is received from the HiRDB server.)
Request interval timeout: 600 seconds
For an SQL Server
Timeout while waiting to acquire memory: -1 (For details about the operations when -1 is specified, see the SQL Server documentation)
Unlock waiting timeout: -1 (Continues to wait until the lock is released)
For XDM/RD E2
Unlock waiting timeout: None (The timeout period is not monitored)
CPU timeout during SQL execution: 10 seconds
SQL execution timeout: 0 seconds (The timeout period is not monitored)
Transaction timeout: 600 seconds
Response timeout: 0 seconds (The HiRDB client continues to wait until a response is received from the XDM/RD E2 server.)
#
In Oracle, there is no default value for the unlock waiting timeout.