Troubleshoot: Naming service

The name service is a J2EE service which publishes and provides access to resources such as connection pools, enterprise beans, message listeners, etc, to client processes. If you have problems in accessing a resource which otherwise appears to be healthy, the naming service might be involved. Use these resources to determine the cause of the problem.

• Check the log files of the server for errors. Messages starting with NMSV are related to the Naming Service. For information on the log files and where they are located, see WebSphere Application Server log files.

• Use the Log Analyzer link to view the IBM service log of the server which is hosting the resource you are trying to access and check for error and warning messages. For more information on the Log Analyzer tool, see Monitor the WebSphere Application Server environment by using the Log Analyzer.

• With WebSphere Application Server running, use the dumpNameSpace script to view the resources bound into the name space for the application server. For more information on the dumpNameSpace script, see the The dumpNameSpace script topic in Application Development. This command results in a display of the objects in the name space, including the path and object name. Note that in a Network Deployment environment, there is a distributed name space. This means there are several name services, and each name service has a different name space. Be sure you connect to the same name service (by using the same host and port in the initial context) that the client experiencing the problem is. For more information, see the Java Naming and Directory Interface (JNDI) topic in Programming.

  If the object a client needs to access does not appear in the name space, use the administrative console to verify that:

  • The server hosting the target resource is started.
  • The Web module or EJB module, if applicable, hosting the target resource is running.

  • The jndi name of the target resource is correct and updated.

• If you see an exception that appears to be CORBA related ("CORBA" appears as part of the exception name) look for a naming-services-specific CORBA minor code, further down in the exception stack, for information on the real cause of the problem.

• Read the release notes. WebSphere Application Server Release Notes (http://publib.boulder.ibm.com/was400/docs/relnotes502.html) .

• Check the WebSphere Application Server FAQ database .

• Refer to the WebSphere Application Server for iSeries newsgroup .
  This iSeries Technical Support Web-based forum is dedicated to WebSphere Application Server for iSeries.

• Contact IBM support. See Get support for WebSphere Application Server for more information.