2.13.3 Operation during the occurrence of a communication failure in the EJB remote interface
You can choose either of the following operations of the client, when communication failure occurs during invocation of the EJB method defined as remote interface from the EJB client:
- Re-establish the connection and resend the request
- Neither re-establish the connection nor resend the request
The settings for using this functionality are specified as properties of a J2EE server or the EJB client application.
Note that in the case of an EJB client application, you can also specify in API (setProperty method of java.lang.System class). For defining in the java.lang.System.setProperty method, specify the settings after starting the process of the EJB client application and before invoking the methods of the Enterprise Bean for the first time.
- Organization of this subsection
- (1) Communication for which the settings are enabled
- (2) Recommended settings
(1) Communication for which the settings are enabled
The operations during communication failure are enabled when communication failure occurs during the invocation of the EJB method defined as the remote interface. Invocation of the EJB method indicates the following:
- Invocation of EJB from a Web application
- Invocation of EJB from the EJB client
- Invocation of EJB from another EJB
The following figure shows the communication for which the settings are enabled:
Figure 2-33 Communication for which the settings are enabled
![[Figure]](figure/zu023000.gif)
Note that the settings are disabled in the following cases:
- Invocation of the EJB method defined as a local interface
- Invocation of the EJB method defined as a remote interface within the range in which optimization of local invocation is enabled
- Invocation of the Naming Service
(2) Recommended settings
Depending upon the system type, Hitachi recommends the following settings:
- In the case of a search and reference node system
- Hitachi recommends that you specify the settings for re-establishing the connection and resending the requests. Consequently, the results can be acquired without facing failure in requests.
- In the case of an update node system
- Hitachi recommends that you specify the settings for not executing either re-establishment of the connection or resending of requests. In an update node system, if you specify the settings for re-establishing the connection and resending the requests, there is a risk of sending duplicate requests.