2.9.5 Notes on the naming service error detection functionality

This subsection describes the notes on the naming service error detection functionality.

Organization of this subsection
(1) Unlock timing
(2) Differences in behavior until 07-60
(3) Checking the viability of the naming management functionality

(1) Unlock timing

When the naming service error detection functionality is not used, the failed naming service is successfully searched from the client application immediately after the naming service and J2EE server are restarted.

However, when the naming service error detection functionality is used, the lock can only be released at the sweep interval. In the naming management functionality, if the sweep interval does not lapse after the naming service stops, the connection is not established to the actual naming service. In other words, maximum sweep interval time is necessary after the recovery of the naming service functionality until the search is successful. When the naming service error detection functionality is used, we recommend that you specify a short time (recommended value 60) in the sweep interval setup time (value of the ejbserver.jndi.cache.interval property).

(2) Differences in behavior until 07-60

In Application Server versions until 07-60 and in version 08-00 and later, the lock timing is different. In version 08-00 and later, in addition to the sweep interval lapse timing, the operating status is checked when the naming service is searched from the client application.

(3) Checking the viability of the naming management functionality

When the naming service error detection functionality is used to check the operating status, the naming service might be considered to have stopped when there is a temporary network error and there is no response due to a high load on the server and during a full garbage collection.