The following figure shows the RMI-IIOP communications (for which a timeout can be specified) working with/without CTM, and also explains the range of timeout:

Figure 2-14 Communications for which a timeout can be specified (when CTM linkage exists)

Figure 2-15 Communications for which a timeout can be specified (when CTM linkage does not exist)

The timeout for RMI-IIOP communications can be set up at three locations that are indicated by A, B, and C in the figure.

• In the case of A
  The timeout is enabled for all the RMI-IIOP communications from steps 1 to 6 in Figure 2-14 and Figure 2-15. The timeout is set up in the definition file. For details on how to set up the timeout in the definition file, see 2.11.8 (1) Setting up a timeout for the RMI-IIOP communication (setting up a J2EE server and EJB client applications).
  
• In the case of B
  The timeout is enabled for the communication with the CORBA Naming Service indicated in steps 1 and 2 in Figure 2-14 and Figure 2-15. The timeout is set up in the definition file. For details on how to set up a timeout in the definition file, see 2.11.8 (1) Setting up a timeout for the RMI-IIOP communication (setting up a J2EE server and EJB client applications).
  
• In the case of C
  The timeout is enabled for the API communication indicated in steps 4 to 6 in Figure 2-14 and Figure 2-15.
  In an EJB client application, specify the timeout period of API communication until create - business method - remove is set by using the API (methods of RequestTimeoutConfigFactory class and RequestTimeoutConfig class), during development of the application. For details on how to set up using the API, see 2.11.7 Implementing a timeout for RMI-IIOP communications.
  

Use this functionality to specify the communication timeout for ORB. In other words, the communication timeout is set for all the RMI-IIOP communications below ORB.

The time of setting a timeout value is during the execution of the first new javax.naming.InitialContext() after invocation of the client.

Even if you do not use the CORBA Naming Service, when you use this functionality, execute new javax.naming.InitialContext() at the beginning of client processing.

If a response is not returned for the request from the client within the value specified in the properties, the request is cancelled as a timeout. When a communication timeout occurs due to this functionality, an java.rmi.RemoteException (org.omg.CORBA.TIMEOUT) exception is thrown. In a client using this functionality, the occurrence of this exception must be considered during invocation of business methods of the Enterprise Beans.