Express (Distributed operating systems), v8.0 > Reference > Messages
NMSV
NMSV0001W: Name server already initialized, ignoring this request to initialize again.
Explanation The name server should be initialized only once, but there was an attempt to initialize it a second time. Action This message is to aid in problem diagnosis and can be ignored if no external symptoms are experienced.
NMSV0002W: WsnNameService bootstrap object created with no properties.
Explanation No properties were supplied to the name server to create a bootstrap object. Action This message is to aid in problem diagnosis and can be ignored if no external symptoms are experienced.
NMSV0003E: Name server initialization failed. Cannot obtain host name for this host.
{0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0005E: Name server initialization failed. Cannot create the LDAP name tree.
{0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0006E: Name server initialization failed. Name server implementation type of "{0}" is not supported in this release.
{1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0007E: Name server initialization failed. Name server implementation type of "{0}" is not recognized as a valid type.
{1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0008E: Name server initialization failed. Could not create a root context IOR. The name server implementation type is "{0}".
{1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0009E: Name server initialization failed. Unable to create name server bootstrap object.
{0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0010E: Name server initialization failed. Initialization of the WLM Bootstrap Service failed.
{0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0011E: Unable to start bootstrap server using port {0}. Verify that no servers or other processes are already using the bootstrap server port. Also verify that the bootstrap server is being started with a user ID which has sufficient (e.g., root, Administrator) privileges.
{1}
Explanation The name server cannot be initialized. An error occurred while attempting to start the bootstrap server. Action Make sure the bootstrap server port is not already in use by any other server processes. This error can occur when the product name server has already been started. In addition, make sure that the bootstrap server is being started with a user ID which has sufficient user privileges. On AIX, HP-UX, Linux and Solaris operating systems, the server must be running as root. On Windows operating systems, the user ID must must be a local Windows user ID that is in the administrative group and has the advanced user rights "Act as part of the operating system" and "Log on as a service." Refer to installation topics in the information center for more information.
NMSV0012E: Name server initialization failed. Cannot create the CosNaming name tree.
{0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0015E: Name server initialization failed. Could not build the System Name Space.
{0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0016E: Internal implementation error. Unexpected InvalidNameException thrown by WsnName while converting an internally generated name string "{0}" to a CosName. Throwing a CosNaming InvalidName exception.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0017E: Name server initialization failed. Unable to register initial reference "{0}".
{1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0018I: Name server available on bootstrap port {0}.
Explanation Informational message indicating the port number opened as the bootstrap port. Action No action is necessary.
NMSV0019I: Opening of the bootstrap port has been suppressed by the setting of name server custom property "BootstrapPortEnabled" to a value of "false". Bootstrap port {0} not open.
Explanation Informational message indicating that the bootstrap port has been disabled. Action No action is necessary.
NMSV0100E: new_context: Unbound context instances not allowed. Throwing NO_IMPLEMENT exception.
Explanation The method, new_context, part of the CosNaming::NamingContext interface, is not supported. Action A client program invoked the new_context method, which is not supported. Clients should use the bind_new_context method.
NMSV0101E: The name syntax property "{0}" is set to an unrecognized value of "{1}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0102E: Unexpected InvalidNameException thrown by WsnName while converting the INS name string "{0}" to another format.
Explanation The CosNaming name server cannot convert a name conversion for internal processing. The name specified for a configured name binding might not be valid. Action If the message is accompanied with another Name Service warning related to configured name bindings, change the configured binding name to a valid binding name.
NMSV0103E: A zero-length CosNaming::NameComponent array was specified. Throwing InvalidName exception.
Explanation An empty name (zero name components) was passed to the CosNaming server. Empty names are not valid. Action If the CosNaming client is a customer-provided application, this is a user error.
NMSV0104E: CosNaming::NameComponent[{0}] contains a null id or kind field. Throwing InvalidName exception.
Explanation A component in a name passed to a method in the product name server implementation of CosNaming::NamingContext contained a null id or kind field. A null value for an id or kind field is not valid. Action If the CosNaming client is a customer-provided application, this is a user error.
NMSV0105E: Cannot convert a CosName to a valid INS name.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0107E: An unexpected error occurred. Mapping to CORBA UNKNOWN.
Explanation An error occurred when processing a CosNaming name server request. Action See the trace output for more details about the origin of the problem.
NMSV0109E: CosNaming server caught exception: AdapterAlreadyExistsException.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0110E: CosNaming server caught exception: InvalidServantException.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0111W: A WebSphere Base Application Server name space is being federated to another WAS name space. This type of name space federation is not supported and may produce incorrect results.
Explanation The Naming Service has detected that the name space federation between two application servers is not valid. As a result, the lookup operation might not work correctly. Action Correct the name space federation between the two application servers.
NMSV0301E: An error occurred during deserialization of the JNDI context "{0}" in a local name space such as a java: URL name space.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0302E: NamingManager.getURLContext returned a null Context for the scheme "{0}".
Explanation A URL was passed to a JNDI Context method, which then invoked the JNDI Naming Manager to return the Context identified by the URL. The Naming Manager method which was invoked returned a null value. Action This problem is probably the result of an incorrect configuration. Make sure that the factory for the scheme of the specified URL can be located from the value of the property, java.naming.factory.url.pkgs, found in the Context's environment.
NMSV0303E: Exception occurred in NamingManager.getURLContext for the scheme: "{0}".
Explanation A URL was passed to a JNDI Context method, which then invoked the JNDI Naming Manager to return the Context identified by the URL. The Naming Manager invocation failed. Action This problem is probably the result of an incorrect configuration. Make sure that the factory for the scheme of the specified URL can be located from the value of the property, java.naming.factory.url.pkgs, found in the Context's environment. The trace output may contain additional diagnostic information.
NMSV0304W: There was an attempt to set the java URL name space accessor more than once.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0305E: A NamingException occurred while getting the next object in the UrlBindingEnumeration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0306E: The scheme or package name for a URL-based name space was not set.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0307E: A java: URL name was used, but Naming was not configured to handle java: URL names. The likely cause is a user in error attempting to specify a java: URL name in a non-J2EE client or server environment. Throwing ConfigurationException.
Explanation Only JNDI clients which are running in a J2EE client or server environment can specify java: URL names in JNDI interface method calls. Action Make sure that the JNDI client using a java: URL name is running in a J2EE client or server environment.
NMSV0308W: javaURLContextFactory cannot create a javaURLContext object because there is no java URL name space currently accessible from the executing thread.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0309W: The operation on the context "{0}" cannot be completed. All contexts under java:comp/env are environment contexts and are read-only.
Explanation Enterprise beans only have read access to environment naming contexts. Environment name contexts include java:comp/env and its subcontexts. Action We cannot perform update operations on environment naming contexts. To bind a new object, use a name that does not start with java:comp/env.
NMSV0310E: A JNDI operation on a "java:" name cannot be completed because the server runtime is not able to associate the operation''s thread with any J2EE application component. This condition can occur when the JNDI client using the "java:" name is not executed on the thread of a server application request. Make sure that a J2EE application does not execute JNDI operations on "java:" names within static code blocks or in threads created by that J2EE application. Such code does not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on "java:" names. Exception stack trace:
{0}
Explanation A JNDI operation on a "java:" name must be performed on the thread of a server application request Action Make sure that a J2EE application does not execute JNDI operations on "java:" names within static code blocks or in threads created by that J2EE application. Such code does not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on "java:" names.
NMSV0401W: The name "{0}" is invalid. The LDAP plug-in for JNDI could not perform an internal name conversion.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0402E: Cannot convert the JNDI name "{0}" to an LDAP name string.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0501W: Ignored an InvalidPropertyName exception from the CosNaming name server.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0502W: The class "com.ibm.ejs.ns.jndi.CNInitialContextFactory" has been deprecated. It has been replaced with "com.ibm.websphere.naming.WsnInitialContextFactory".
Explanation The initial context factory for WebSphere has changed. The old one will work, but some time in the future it will no longer be available. Action Begin using the new initial context factory as soon as possible.
NMSV0601E: Naming Service unavailable. Null initial context returned from ORB.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0602E: Naming Service unavailable. A communications error occurred.
Explanation A connection to the name server could not be made when attempting create an initial context. Action Typical causes are that the provider URL is incorrect or that the name server identified by the provider URL is not running. Make sure that the name server is running and that the host and port in the provider URL are correct. Also, make sure that the host identified in the provider URL can be ping'ed from the machine on which the JNDI client is running. Refer to the trace output accompanying this message for more information about the root cause.
NMSV0603E: Naming Service unavailable. Could not get the root context.
Explanation An unknown error occurred while attempting to obtain the initial context from the ORB. Action For more information about the root cause, refer to any additional trace output accompanying this message.
NMSV0604E: Exception thrown in Referenceable.getReference().
Explanation While processing a JNDI bind or rebind operation on a javax.naming.Referenceable object, a call to the method, getReference(), on the object resulted in an exception. Action The Referenceable object could not be processed for some unknown reason. Refer to the trace output accompanying this message for more details on the root cause.
NMSV0605W: A javax.naming.Reference object looked up from the context "{0}" with the name "{1}" was sent to the JNDI Naming Manager and an exception resulted. Reference data follows:
Reference Factory Class Name: {2}
Reference Factory Class Location URLs: {3}
{4}
Exception data follows:
{5}
Explanation While executing a JNDI lookup or listBindings operation on a javax.naming.Reference object, a call to the JNDI Naming Manager to process the object failed. It is possible that some class required by the Reference object's factory could not be loaded or some exception occurred while instantiating the factory object. It is also possible that some class required by the factory to instantiate an object from the Reference object could not be loaded, or that some exception occurred while the factory was instantiating the object. Action Ensure that the factory class can be loaded from the calling environment and that the class instantiated by the factory can be loaded. Actions on exceptions originating from the factory depend on the specific factory's implementation.
NMSV0606E: Object is not of any type which can be bound.
Explanation The JNDI bind or rebind method was passed an object which is of a type that cannot be bound. Allowed object types include CORBA objects (which includes deployed enterprise beans), JNDI contexts of the same type as the context object being invoked, javax.naming.Referenceable, javax.naming.Reference, and java.io.Serializable. Action Attempt to bind or rebind only objects of the above types.
NMSV0607E: The Context at name path "{0}" was passed a null name to the method "{1}".
Explanation A JNDI context method was passed a null name. Null names are not valid. Action Use an appropriate name for the desired JNDI operation.
NMSV0608E: The Context at name path "{0}" was passed an empty name to the method "{1}".
Explanation A JNDI context method was passed an empty name. JNDI context methods except for lookup, list, and listBindings, do not accept empty names. Action Use an appropriate name for the desired JNDI operation.
NMSV0609W: A Reference object looked up from the context "{0}" with the name "{1}" was sent to the JNDI Naming Manager and was returned unprocessed. Reference data follows:
Reference Factory Class Name: {2}
Reference Factory Class Location URLs: {3}
{4}
Explanation While executing a JNDI lookup or listBindings operation on a javax.naming.Reference object, a call to the JNDI Naming Manager to process the object returned the original Reference object, indicating that no processing was done. This is most likely not the intended result. It is possible that the factory class required to process the Reference could not be determined or loaded. Action Make sure that the Reference object contains a factory class name. Ensure that the factory class can be loaded from the calling environment.
NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow:
Context implementation: {0}
Context method: {1}
Context name: {2}
Target name: {3}
Other data: {4}
Exception stack trace: {5}
Explanation Some javax.naming.Context implementation has raised an exception. Data related to the exception is included with the message. Action If the exception triggering this message is the result of normal operation, the message can be ignored. If the exception is not expected, refer to the diagnostic information included with the message to help determine the cause.
NMSV0611E: A Referenceable.getReference() returns null.
Object to bind: {0}
Referenceable object: {1}
Explanation While processing a JNDI bind or rebind operation on a javax.naming.Referenceable object, a call to the method, getReference(), on the object returns null, which violates the JNDI API. Action Verify that the method getReference() on the Referenceable object returns a non-null Reference object. According to the JNDI API, getReference() on a Referenceable object should return a non-null Reference of this object.
NMSV0612W: A NameNotFoundException occurred on an indirect lookup on the name "{0}". The name "{0}" maps to a JNDI name in deployment descriptor bindings for the application performing the JNDI lookup. Make sure that the JNDI name mapping in the deployment descriptor binding is correct. If the JNDI name mapping is correct, make sure the target resource can be resolved with the specified name relative to the default initial context. NameNotFoundException data follows:
{1}
Explanation The target resource cannot be resolved with the specified name relative to the default initial context. Action Make sure that the JNDI name mapping in the deployment descriptor binding is correct. If the name mapping is correct, make sure the target resource can be resolved with the specified name relative to the default initial context.
NMSV0701W: An IndirectJNDILookup object was created with an empty name. Lookups using this object will fail.
{0}
Explanation An IndirectJNDILookup object was created with an empty name. Indirect lookups require non-empty names. Action Do not create IndirectJNDILookup objects with empty names.
NMSV0710W: Configured Bindings: "{0}" field was not set in {1}
object: {2}
name in name space: {3}
XML location: {4} level of "namebindings.xml" file.
Explanation Some required fields or attributes are missing (or empty) in a name space binding defined in the specified namebindings.xml file. Either the file was edited incorrectly or became corrupted for some reason. Action Delete the problem namebindings.xml file and recreate the configured bindings for that configuration scope through wsadmin or the administrative console.
NMSV0711W: Configured Bindings: name already bound. Exception data:
{0}
Explanation A binding already exists in the name space with the same name as this configured binding. Action Use a different name or make sure the configured binding is in the correct place in name space.
NMSV0712W: Configured Bindings: Cannot create an intermediate context for the configured binding "{0}" relative to the context "{1}" because of a name conflict with an object other than another configured context binding.
Explanation When a binding with a compound name is configured, all intermediate contexts must either not already exist or be contexts created from other configured bindings. Action Use a different name or make sure the configured binding is in the correct place in name space.
NMSV0713W: Configured Bindings: Cannot create the configured binding "{0}" relative to the context "{1}" because of an unexpected error.
{2}
Explanation Some error occurred when creating an intermediate context for a configured binding. Action Make sure the name is valid and that it does not conflict in any way with existing bindings in the name space.
NMSV0714W: Invalid Configuration:
The port number "{0}" of end point named "{1}" is being used by end point "{2}" in server "{3}".
Explanation A duplicate port number has been assigned in the same server. The server might not work properly. Action Make sure that each endpoint in each server configuration has an unique port number assigned, then restart the server.
NMSV0715W: Configured Bindings: The server "{1}" or node "{0}" specified in an EJB configured binding does not exist. Configured binding info:
Binding name: {2}
Name in name space: {3}
Scope: {4}.
Explanation The non-clustered application server with name and node specified in the XML file has not been configured in this cell. Action Make sure the node name and server name identify a configured non-clustered server.
NMSV0716W: Configured Bindings: The cluster "{0}" specified in an EJB configured binding does not exist. Configured binding info:
Binding name: {1}
Name in name space: {2}
Scope: {3}.
Explanation The cluster with the name specified in the XML file has not been configured in this cell. Action Make sure the cluster name indentifies a configured cluster.
NMSV0717W: Configured Bindings: The value "{0}" for the "{1}" field is invalid.
Configured binding type: {2}
Binding name: {3}
Name in name space: {4}
Scope: {5}.
Explanation A configured binding was defined with a parameter value that is not valid. Action Correct the configured binding setting shown in the error message.
NMSV0718W: No bootstrap address specified for foreign cell binding "{0}".
Explanation The specified foreign cell binding does not contain any bootstrap address information. Action Correct the foreign cell binding specified in the error message.
NMSV0719W: Attribute "{0}" is not set in foreign cell binding "{1}".
Explanation A required attribute is missing in the specified foreign cell binding. Action Correct the foreign cell binding attribute specified in the error message.
NMSV0720W: The value "{0}" of attribute "{1}" is invalid in foreign cell binding "{2}".
{3}
Explanation The specified foreign cell binding is defined with an invalid value. Action Correct the foreign cell binding attribute specified in the error message.
NMSV0750W: Invalid binding found in the XML file "{0}". The entry for name "{1}" has a nameBindingType value of "contextLinked", but its contextId value is null. This binding is being ignored. Updates to the corresponding persistent name space partition have been disabled.
Explanation During server startup, while the name server was reading in the specified XML file, a binding entry that is not valid was found in the XML file. The entry is being ignored. Until the problem is corrected, update operations on contexts backed by the specified XML file are disabled. Action Remove the binding entry that is not valid from the XML file. The context can then be rebound if necessary.
NMSV0751W: Could not add binding "{1}" to the name space. The binding data is contained in the XML file "{0}". Updates to the corresponding persistent name space partition have been disabled. Error information follows:
{2}
Explanation During server startup, while the name server was reading in the specified XML file, an error occurred while attempting to add the binding to the name space. The entry is being ignored. Until the problem is corrected, update operations on contexts backed by the specified XML file are disabled. Action If the problem cannot be resolved with the included error information, remove the binding entry that is not valid from the XML file. The context can then be rebound if necessary.
NMSV0752W: Invalid binding found in the XML file "{0}". The entry for name "{1}" has a nameBindingType value of "contextIOR", but the object for the IOR is not a context. This binding is being ignored. Updates to the corresponding persistent name space partition have been disabled.
Explanation During server startup, while the name server was reading in the specified XML file, a binding entry that is not valid was found. The entry is being ignored. Until the problem is corrected, update operations on contexts backed by the specified XML file are disabled. Action Remove the binding entry that is not valid from the XML file. The context can then be rebound if necessary. If necessary, delete the file entirely. Deleting the file effectively removes all persistent bindings from the associated name space partition.
NMSV0753W: Invalid binding found in the XML file "{0}". The entry for name "{1}" has a nameBindingType value of "contextIOR", but the stringifiedIOR value is null. This binding is being ignored. Updates to the corresponding persistent name space partition have been disabled.
Explanation During server startup, while the name server was reading in the specified XML file, a binding entry that is not valid was found. The entry is being ignored. Until the problem is corrected, update operations on contexts backed by the specified XML file are disabled. Action Remove the binding entry that is not valid from the XML file. The object can then be rebound if necessary. If necessary, delete the file entirely. Deleting the file effectively removes all persistent bindings from the associated name space partition.
NMSV0754W: Invalid binding found in the XML file "{0}". The entry for name "{1}" has a nameBindingType value of "objectJava", but the serializedBytesAsString value is null. This binding is being ignored. Updates to the corresponding persistent name space partition have been disabled.
Explanation During server startup, while the name server was reading in the specified XML file, a binding entry that is not valid was found. The entry is being ignored. Until the problem is corrected, update operations on contexts backed by the specified XML file are disabled. Action Remove the binding entry that is not valid from the XML file. The object can then be rebound if necessary. If necessary, delete the file entirely. Deleting the file effectively removes all persistent bindings from the associated name space partition.
NMSV0755W: Invalid binding found in the XML file "{0}". The entry for name "{1}" has a nameBindingType value of "objectJava" and the serializedBytesAsString value is invalid. This binding is being ignored. Updates to the corresponding persistent name space partition have been disabled.
Explanation During server startup, while the name server was reading in the specified XML file, a binding entry that is not valid was found. The entry is being ignored. Until the problem is corrected, update operations on contexts backed by the specified XML file are disabled. Action Remove the binding entry that is not valid from the XML file. The object can then be rebound if necessary. If necessary, delete the file entirely. Deleting the file effectively removes all persistent bindings from the associated name space partition.
NMSV0756W: Invalid binding found in the XML file "{0}". The entry for name "{1}" has a nameBindingType value of "contextURL" but the insURL value is null. This binding is being ignored. Updates to the corresponding persistent name space partition have been disabled.
Explanation During server startup, while the name server was reading in the specified XML file, a binding entry that is not valid was found. The entry is being ignored. Until the problem is corrected, update operations on contexts backed by the specified XML file are disabled. Action Remove the binding entry that is not valid from the XML file. The object can then be rebound if necessary. If necessary, delete the file entirely. Deleting the file effectively removes all persistent bindings from the associated name space partition.
NMSV0757W: Invalid binding found in the XML file "{0}" under the context with the name "{1}". The binding has a nameComponent value of "{2}", which is an invalid name component. This binding is being ignored. Updates to the corresponding persistent name space partition have been disabled.
Explanation The binding name for the entry is not valid. The name must be a valid CORBA INS name string for a single name component. The entry is being ignored. Until the problem is corrected, update operations on contexts backed by the specified XML file are disabled. Action Change the binding name to a valid name which does not conflict with other binding names, or remove the binding entry that is not valid from the XML file and rebind the object if necessary. If necessary, delete the file entirely. Deleting the file effectively removes all persistent bindings from the associated name space partition.
NMSV0758E: The name server could not acquire a Configuration Repository handle. Persistent name binding data cannot be processed. Error information follows:
{1}
Explanation In order for the name server to process any persistent name binding information, it needs a Configuration Repository client handle to access persistent name binding XML files. An attempt to acquire a Configuration Repository handle failed. Action Restart the server. Refer to the diagnostic data provided to determine the root cause of the problem.
NMSV0759E: An error occurred on a file extract operation for the persistent name binding XML file "{0}". Persistent name binding information could not be read in. Error information follows:
{1}
Explanation In order to read in persistent name binding data from an XML file during name server initialization, the name server must extract the XML file from the Configuration Respository. The extract operation failed. Action Restart the server. Refer to the diagnostic data provided to determine the root cause of the problem.
NMSV0760E: An error occurred on a file checkout operation for the persist name binding XML file "{0}". Persistent name binding update could not be completed. Error information follows:
{1}
Explanation In order to process an update operation on a persistent name binding, the name server must check out the persistent name binding XML file from the Configuration Respository. The checkout operation failed. Action Restart the server. Refer to the diagnostic data provided to determine the root cause of the problem.
NMSV0761E: An error occurred on a file checkin operation for the persistent name binding XML file "{0}". Persistent name binding update could not be completed. Error information follows:
{1}
Explanation In order to process an update operation on a persistent name binding, the name server must check out the persistent name binding XML file from the Configuration Respository, update the file, and check it in. The checkin operation failed. Action Restart the server. Refer to the diagnostic data provided to determine the root cause of the problem.
NMSV0762E: An error occurred on a file unlock operation for the persistent name binding XML file "{0}". Error information follows:
{1}
Explanation After experiencing some problem processing a persistent name binding XML file, a Configuration Respository request to unlock the file failed. Action Restart the server. Refer to the diagnostic data provided to determine the root cause of the problem.
NMSV0763E: An error occurred while processing the persistent name binding XML file "{0}". Update operation could not be completed. Error information follows:
{1}
Explanation The name server experienced some problem processing a persistent name binding XML file. The update operation failed. Action Restart the server. Refer to the diagnostic data provided to determine the root cause of the problem.
NMSV0800W: Exception encountered loading configuration file "{0}".
{1}.
Explanation An error occurred when loading configuration file. As a result, name server custom property settings might be ignored. Action The action required depends on the root cause of the problem. Refer to the diagnostic data provided to determine the root cause of the problem.
NMSV0801W: Exception encountered loading file "{0}" from clusters directory "{1}". Cluster configuration information has been ignored.
{2}.
Explanation An error occurred when loading the specified configuration file. As a result, the name server's system name space structure might not reflect the entire cell configuration. Action The action required depends on the root cause of the problem. Refer to the diagnostic data provided to determine the root cause of the problem.
NMSV0802W: Found the configuration document "{0}" as part of the dmgr''s node configuration. The dmgr''s node is not a valid location for node-scoped configured name bindings.
Explanation Name bindings were found in the dmgr's node configuration. Node-scoped configured bindings are bound in the name space under the node's node persistent root. Since there is no node persistent persistent root for the dmgr's node, this node is not a valid location for node-scoped configured name bindings. Action Make sure that we have selected the right node and scope for the configured bindings.
NMSV0803W: Duplicate server name encountered. Ignoring server "{0}" on node "{1}" (endpoint: {2}).
Explanation Two servers with the same name were found in the specified node. As a result, the name server's system name space structure may not reflect the entire cell configuration. All server names within a node must be unique. Action Make sure that all server names are unique within a node.
NMSV0804W: Missing host name in bootstrap address of server "{0}" in node "{1}". Skipping this server configuration and continuing.
Explanation The bootstrap address configuration for the specified server does not contain a host name. As a result, the name server's system name space structure will not include the specified server. Action Make sure all bootstrap addresses include a host name and port number.
NMSV0805W: Missing port number in bootstrap address of server "{0}" in node "{1}". Skipping this server configuration and continuing.
Explanation The bootstrap address configuration for the specified server does not contain a port number. As a result, the name server's system name space structure will not include the specified server. Action Make sure all bootstrap addresses include a host name and port number.
NMSV0806W: The bootstrap address "{0}" configured for this server conflicts with the bootstrap address configured for server "{1}" on node "{2}". Ignoring the conflicting server.
Explanation Encountered another server configured with the same bootstrap host and port as this server. The conflicting server is being ignored. As a result, the name server's system name space structure may not reflect the entire cell configuration. Action Make sure that all servers are configured with the correct bootstrap addresses and that all bootstrap ports on a host are unique.
NMSV0807W: The bootstrap address "{0}" configured for server "{1}" on node "{2}" conflicts with the bootstrap port of another server. Ignoring the specified server.
Explanation Encountered two servers configured with the same bootstrap address. The one specified in the error message is being ignored. As a result, the name server's system name space structure may not reflect the entire cell configuration. Action Make sure that all servers in the cell are configured with the correct bootstrap host and that all bootstrap ports on a host are unique.
NMSV0808W: Configuration for cluster "{2}" specifies a non-existent member server. Ignoring server "{0}" on node "{1}".
Explanation Cannot find the specified server in the cell configuration. A cluster member is probably incorrectly specified in the cluster configuration. Action Make sure that members configured for a cluster include only servers which exist in the cell configuration.
NMSV0809W: Opening of the bootstrap port cannot be disabled in a server not configured as a standalone server.
Explanation Every server opens the bootstrap port defined for it unless it has been disabled. The bootstrap port of a server can be disabled only if the server is running as a standalone server. Managed servers, node agents, and dmgrs, for example, cannot have their bootstrap port disabled. Action Do not set the BootstrapPortEnabled name server custom property to false for a server not configured as a standalone server.
NMSV0810W: Name Server Configuration Warning: Due to previous warnings it is possible the name space will not be constructed correctly.
Explanation Some Name Server configuration warning have been issued prior to this message. Most likely the name space will not be constructed correctly. Action Try to resolve previous warnings first.
NMSV0811W: Name Server Configuration Warning: {0}
Explanation Name Server configuration warning have been issued with some additional information. Action Look into this additional information to resolve this warning.
NMSV0812W: Configuration changes have occurred which require this server to be restarted.
Explanation Changes have been made to the configuration which affect the name server running in the process associated with this message. The server process must be restarted for these changes to take effect. Action Restart the server which received this warning message.
NMSV0813W: An error occurred while updating the name space in response to configuration changes.
Explanation Changes have been made to the configuration which affect the name server running in the process associated with this message. An error occurred while attempting to update the name space. The name space may not accurately reflect the current configuration. Action Restart the server which received this warning message.
NMSV0814W: An error occurred while updating the name space in response to configuration changes. Error data:
{0}
Explanation Changes have been made to the configuration which affect the name server running in the process associated with this message. An error occurred while processing the new configuration data in an effort to update the name space to reflect the configuration changes. The name space may not accurately reflect the current configuration. Action Restart the server which received this warning message.
NMSV0815W: Name server custom property value "{0}" is invalid for name server custom property: "{1}". Will use default value instead.
Explanation A wrong value has been specified in name server custom property. Action Make sure the property value is valid. For BootstrapPortEnabled name server custom property, the value must be either "true" or "false". For naming.systemNameSpace.scope, valid values are "cell", "node", and "server".
NMSV0816W: Name server custom property "{0}" has been changed. This will require a manual server restart.
Explanation Changes have been made to the name server custom property which affect the name server running in the process associated with this message. The server process must be restarted for these changes to take effect. Action Restart the server which received this warning message.
NMSV0818I: Name server custom property "{0}" set to "{1}".
Explanation Informational message indicating a name server custom property setting. Action No action is necessary.
NMSV0819W: No deployments directory found for application. Ignoring application "{0}".
Explanation An inconsistency in the configuration for the specified application was detected. The applications sections of the name space structure might not reflect the application correctly. Action More info at:
NMSV0820W: No deployment configuration found for application. Ignoring deployment "{1}" of application "{0}".
Explanation An inconsistency in the configuration for the specified application deployment was detected. The applications sections of the name space structure might not reflect the application correctly. Action More info at:
NMSV0821W: An unexpected error occurred while reading application deployment data. Error data:
{0}
Explanation Could not build the applications section of the name space because of an unexpected error. Action More info at:
NMSV0822W: Duplicate module name encountered. Ignoring module "{0}" (URI: {1}) in application "{2}".
Explanation Two modules with the same name were found in the specified node. As a result, the name server's application name space structure may not reflect the entire application configuration. All module names within an application must be unique. Action Make sure that all module names are unique within an application. In particular, verify that the deployment descriptors for two modules do not specify the same module name.
NMSV0901E: An unexpected error occurred.
Explanation Some unexpected error occurred. Action Refer to the diagnostic data provided to determine the root cause of the problem.
NMSV0902E: An error occurred while serializing an object.
Explanation An error occurred while attempting to serialize an object. This error probably occurred during a JNDI bind or rebind operation. Action One possible cause is that some object encountered during the serialization process is not serializable. For more information about the root cause, see the trace output which accompanies this message.
NMSV0903E: An error occurred while deserializing an object.
Explanation An error occurred while attempting to deserialize an object. This error probably occurred during a JNDI lookup or listBindings operation. Action The most likely cause for this problem is not having the required class or classes in the JNDI client CLASSPATH. The trace output should contain more details, such as the class name that could not be found.
NMSV0904W: Ignored InvalidNameException while converting a CosName to a String for internal processing.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0905E: Failed to create Class object for the class "{0}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0906E: Could not create an instance of the class "{0}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0907E: Could not invoke method "{0}" on object of type "{1}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
NMSV0908W: The file com/ibm/websphere/naming/jndiprovider.properties could not be loaded.
Explanation The com/ibm/websphere/naming/jndiprovider.properties file could not be loaded Action Ensure that the .jar file containing the com/ibm/websphere/naming/jndiprovider.properties file is located where it can be found by the class loader. If the file is accessable to the class loader, look for any other messages that may identify the problem.
NMSV0910E: A Naming error occurred. Details follow:
{0}
Explanation An undocumented naming error occurred. Action Refer to the diagnostic data provided to determine the root cause of the problem.
NMSV0911E: No initial context factory implementation is defined for com.ibm.naming.websphere.WsnInitialContextFactory. Make sure a WebSphere jar file that contains com/ibm/websphere/naming/jndiprovider.properties can be located by the class loader.
Explanation A property in the file com/ibm/websphere/naming/jndiprovider.properties is set with the class name of the initial context factory implementation to use. Since the property is not set, the class loader is apparently not locating the containing jar file. Action In your specific WebSphere installation, find the jar file that contains com/ibm/websphere/naming/jndiprovider.properties and make sure your runtime environment is set up so that the class loader will be able to locate it.