ContextRecord
has not been found in a naming context. This may happen if the name asked in the JNDI request doesn't exist. That's why this exception includes a NameNotFoundException
ready to be thrown forward. But the missing record may be resolved. For example, in a distributed configuration a missing record may indicate that the local JNDI server (where the record is missing) is not up to date according to a remote server where the record has been created. In this case, instead of throwing a NameNotFoundException
the JNDI request may be blocked until the update arrives and creates the missing record.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|