NMSV

NMSV0001W: Name server already initialized, ignoring this request to initialize again.
NMSV0002W: WsnNameService bootstrap object created with no properties.
NMSV0003E: Name server initialization failed. Cannot obtain host name for this host. {0}
NMSV0005E: Name server initialization failed. Cannot create the LDAP name tree. {0}
NMSV0006E: Name server initialization failed. Name server implementation type of "{0}" is not supported in this release. {1}
NMSV0007E: Name server initialization failed. Name server implementation type of "{0}" is not recognized as a valid type. {1}
NMSV0008E: Name server initialization failed. Could not create a root context IOR. The name server implementation type is "{0}". {1}
NMSV0009E: Name server initialization failed. Unable to create name server bootstrap object. {0}
NMSV0010E: Name server initialization failed. Initialization of the WLM Bootstrap Service failed. {0}
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}
NMSV0012E: Name server initialization failed. Cannot create the CosNaming name tree. {0}
NMSV0015E: Name server initialization failed. Could not build the System Name Space. {0}
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.
NMSV0017E: Name server initialization failed. Unable to register initial reference "{0}". {1}
NMSV0018I: Name server available on bootstrap port {0}.
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.
NMSV0100E: new_context: Unbound context instances not allowed. Throwing NO_IMPLEMENT exception.
NMSV0101E: The name syntax property "{0}" is set to an unrecognized value of "{1}".
NMSV0102E: Unexpected InvalidNameException thrown by WsnName while converting the INS name string "{0}" to another format.
NMSV0103E: A zero-length CosNaming::NameComponent array was specified. Throwing InvalidName exception.
NMSV0104E: CosNaming::NameComponent[{0}] contains a null id or kind field. Throwing InvalidName exception.
NMSV0105E: Cannot convert a CosName to a valid INS name.
NMSV0107E: An unexpected error occurred. Mapping to CORBA UNKNOWN.
NMSV0109E: CosNaming server caught exception: AdapterAlreadyExistsException.
NMSV0110E: CosNaming server caught exception: InvalidServantException.
NMSV0111W: A WebSphere Base Application Server name space is being federated to another WebSphere Application Server name space. This type of name space federation is not supported and may produce incorrect results.
NMSV0301E: An error occurred during deserialization of the JNDI context "{0}" in a local name space such as a java: URL name space.
NMSV0302E: NamingManager.getURLContext returned a null Context for the scheme "{0}".
NMSV0303E: Exception occurred in NamingManager.getURLContext for the scheme: "{0}".
NMSV0304W: There was an attempt to set the java URL name space accessor more than once.
NMSV0305E: A NamingException occurred while getting the next object in the UrlBindingEnumeration.
NMSV0306E: The scheme or package name for a URL-based name space was not set.
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.
NMSV0308W: javaURLContextFactory cannot create a javaURLContext object because there is no java URL name space currently accessible from the executing thread.
NMSV0309W: The operation on the context "{0}" cannot be completed. All contexts under java:comp/env are environment contexts and are read-only.
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}
NMSV0401W: The name "{0}" is invalid. The LDAP plug-in for JNDI could not perform an internal name conversion.
NMSV0402E: Cannot convert the JNDI name "{0}" to an LDAP name string.
NMSV0501W: Ignored an InvalidPropertyName exception from the CosNaming name server.
NMSV0502W: The class "com.ibm.ejs.ns.jndi.CNInitialContextFactory" has been deprecated. It has been replaced with "com.ibm.websphere.naming.WsnInitialContextFactory".
NMSV0601E: Naming Service unavailable. Null initial context returned from ORB.
NMSV0602E: Naming Service unavailable. A communications error occurred.
NMSV0603E: Naming Service unavailable. Could not get the root context.
NMSV0604E: Exception thrown in Referenceable.getReference().
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}
NMSV0606E: Object is not of any type which can be bound.
NMSV0607E: The Context at name path "{0}" was passed a null name to the method "{1}".
NMSV0608E: The Context at name path "{0}" was passed an empty name to the method "{1}".
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}
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}
NMSV0611E: A Referenceable.getReference() returns null. Object to bind: {0} Referenceable object: {1}
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}
NMSV0701W: An IndirectJNDILookup object was created with an empty name. Lookups using this object will fail. {0}
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.
NMSV0711W: Configured Bindings: name already bound. Exception data:      {0}
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.
NMSV0713W: Configured Bindings: Cannot create the configured binding "{0}" relative to the context "{1}" because of an unexpected error. {2}
NMSV0714W: Invalid Configuration:      The port number "{0}" of end point named "{1}" is being used by end point "{2}" in server "{3}".
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}.
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}.
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}.
NMSV0718W: No bootstrap address specified for foreign cell binding "{0}".
NMSV0719W: Attribute "{0}" is not set in foreign cell binding "{1}".
NMSV0720W: The value "{0}" of attribute "{1}" is invalid in foreign cell binding "{2}". {3}
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.
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}
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.
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.
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.
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.
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.
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.
NMSV0758E: The name server could not acquire a Configuration Repository handle. Persistent name binding data cannot be processed. Error information follows: {1}
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}
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}
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}
NMSV0762E: An error occurred on a file unlock operation for the persistent name binding XML file "{0}". Error information follows: {1}
NMSV0763E: An error occurred while processing the persistent name binding XML file "{0}". Update operation could not be completed. Error information follows: {1}
NMSV0800W: Exception encountered loading configuration file "{0}". {1}.
NMSV0801W: Exception encountered loading file "{0}" from clusters directory "{1}". Cluster configuration information has been ignored. {2}.
NMSV0802W: Found the configuration document "{0}" as part of the deployment manager''s node configuration. The deployment manager''s node is not a valid location for node-scoped configured name bindings.
NMSV0803W: Duplicate server name encountered. Ignoring server "{0}" on node "{1}" (endpoint: {2}).
NMSV0804W: Missing host name in bootstrap address of server "{0}" in node "{1}". Skipping this server configuration and continuing.
NMSV0805W: Missing port number in bootstrap address of server "{0}" in node "{1}". Skipping this server configuration and continuing.
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.
NMSV0807W: The bootstrap address "{0}" configured for server "{1}" on node "{2}" conflicts with the bootstrap port of another server. Ignoring the specified server.
NMSV0808W: Configuration for cluster "{2}" specifies a non-existent member server. Ignoring server "{0}" on node "{1}".
NMSV0809W: Opening of the bootstrap port cannot be disabled in 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.
NMSV0811W: Name Server Configuration Warning: {0}
NMSV0812W: Configuration changes have occurred which require this server to be restarted.
NMSV0813W: An error occurred while updating the name space in response to configuration changes.
NMSV0814W: An error occurred while updating the name space in response to configuration changes. Error data: {0}
NMSV0815W: Name server custom property value "{0}" is invalid for name server custom property: "{1}". Will use default value instead.
NMSV0816W: Name server custom property "{0}" has been changed. This will require a manual server restart.
NMSV0818I: Name server custom property "{0}" set to "{1}".
NMSV0819W: No deployments directory found for application. Ignoring application "{0}".
NMSV0820W: No deployment configuration found for application. Ignoring deployment "{1}" of application "{0}".
NMSV0821W: An unexpected error occurred while reading application deployment data. Error data: {0}
NMSV0822W: Duplicate module name encountered. Ignoring module "{0}" (URI: {1}) in application "{2}".
NMSV0901E: An unexpected error occurred.
NMSV0902E: An error occurred while serializing an object.
NMSV0903E: An error occurred while deserializing an object.
NMSV0904W: Ignored InvalidNameException while converting a CosName to a String for internal processing.
NMSV0905E: Failed to create Class object for the class "{0}".
NMSV0906E: Could not create an instance of the class "{0}".
NMSV0907E: Could not invoke method "{0}" on object of type "{1}".
NMSV0908W: The file com/ibm/websphere/naming/jndiprovider.properties could not be loaded.
NMSV0910E: A Naming error occurred. Details follow: {0}
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.


Terms and conditions for information centers | Feedback

Last updated: June 12, 2013 12:15 PM EDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.naming.util.WsnMessages.dita
File name: com.ibm.ws.naming.util.WsnMessages.html