ContextRecord
indicating that the naming context exists. This may happen in a distributed JNDI configuration when a naming context has not been locally created yet. For example if the context /A has been created on the server 0 and the context /A/B on the server 1. If the server 2 starts, it gets from the server 0 the naming context /A containing a ContextRecord
named B. If a JNDI request is asked about B (e.g. bind /A/B/C) then the server 2 can't find the naming context B because it still didn't get the naming data from server 1. So a MissingContextException
is thrown.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|