MustGather: Java Naming and Directory Interface (JNDI) and naming problems for all releases and editions of V3.5, V4.0, and V5.0

Technote (FAQ)
Problem
MustGather for problems with the WebSphere® Application Server JNDI naming component. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
Solution
If you have already contacted support, continue on to the component-specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Application Server products.


JNDI specific MustGather information
  1. Version of WebSphere Application Server and interim patches that have been installed?
    • For all releases of V4.0, this is found in the following file:

      install_root/properties/com/ibm/websphere/product.xml
    • For all releases of V5, this can be found using the versioninfo command.

  2. For all releases of V5, is this a base or Network Deployment installation?

  3. If an exception has occurred, provide the full stack trace or the log file in which it is contained.

  4. What is the network topology or system environment? How many nodes? Please supply a topology map or describe the topology in words.

  5. Is WebSphere Application Server Security enabled?

  6. Is the client local or remote to the server? If a remote server is involved, is there firewall present?

  7. What type of client is being used (J2EE™ Application, Thin Client, Thick Client, EJB™)?

  8. Provide a code sample that shows the InitialContext and lookup statement. Include the PROVIDER_URL and INITIAL_CONTEXT_FACTORY as set in code, Java™ virtual machine (JVM™) setting, or properties file.

  9. Provide a dumpNameSpace output for the server being queried during the lookup. (specified in the PROVIDER_URL). Refer to the topic dumpNameSpace in the Information Center for details about invocation details. Note that in all releases of V5.0, each server, node agent, and network deployment manager has its own namespace, so the -port option is required when invoking dumpNameSpace if the namespace is not referenced by the default port of 2809. In all releases of V4.0, the name server runs on the admin server.

  10. Provide instructions to reproduce the problem.

  11. Provide a naming trace that could be either from naming server or naming client when you think that the Naming trace will help the problem determination.

  12. Follow instructions tosend diagnostic information to IBM support.

For V5.0 releases, collect the following additional information:
  1. Delete or rename the logs in the install_root/logs directory. If you are running the deployment manager, also delete the logs in the install_root_dmgr/logs directory.

  2. Start the deployment manager (if applicable), the node agent (if applicable), and the Application Server.

  3. Recreate the problem. Write down the approximate system time that the problem occurs.

  4. Run the install_root/bin/collector.sh or the collector.bat files.
    • Do not run this file directly from the bin directory or any other WebSphere directory.
    • Follow the instructions on running the collector tool in the WebSphere Application Server Information Center.
    • Do not use the summary option

  5. If you are running the Network Deployment edition, run the install_root_dmgr/bin/collector.sh or collector.bat file using the same instructions as in step 4.

  6. Follow instructions tosend diagnostic information to IBM support.


For a listing of all technotes, downloads, and educational materials specific to the JNDI/Naming component, search the WebSphere Application Server support site.
Related information
Submitting information to IBM support

Steps to getting support

MustGather: Read first

Troubleshooting guide












Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, JNDI/Naming
Operating system(s): AIX, HPUX, Linux, Multi-Platform, Solaris, Windows
Software version: 3.5, 3.5.1, 3.5.2, 3.5.3, 3.5.4, 3.5.4.1, 3.5.4.2, 3.5.5, 3.5.6, 3.5.7, 3.5.x, 4.0, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7, 4.0.8, 4.0.x, 5.0, 5.0.0, 5.0.1, 5.0.2, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.2.4, 5.0.2.5, 5.0.2.6, 5.0.2.7, 5.0.2.8, 5.0.2.9, 5.0.3, 5.0.x
Software edition: Edition Independent
Reference #: 1143296
IBM Group: Software Group
Modified date: 2004-12-10