MustGather: JNDI and Naming problems in WebSphere Application Server

Technote (troubleshooting)


Problem(Abstract)

Collecting data for problems with the IBM WebSphere Application Server Java Naming and Directory Interface (JNDI). Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.

Resolving the problem

Tab navigation

Collecting data for problems with the IBM WebSphere Application Server Java Naming and Directory Interface (JNDI). Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.

To improve the accuracy of complete data collection, IBM recommends you use the automated data collectors within IBM Support Assistant. Not only will the automated collector gather the equivalent of the manual process, it will also provide a secure file transfer of the collection to IBM.

Collecting data using the IBM Support Assistant Data Collector

    Beginning with WebSphere Application Server V8.0.0.6, the IBM Support Assistant Data Collector (ISADC) tool is bundled with the product and is automatically installed. As a result, you can run the  ISADC tool directly from the app_server_root/bin directory. Note: ISADC is not bundled with the WebSphere Application Server Liberty Profile. For more details, see Using the IBM Support Assistant Data Collector.


  1. Using the ISA Data Collector:
    • To run ISADC from command line, go to your app_server_root/bin directory and run isadc.[sh|bat]

      • To download, install and run ISADC locally:
      • Obtain the IBM Support Assistant Data collector online ISA Data Collector site for WebSphere Application Server.
      • Select the option to collect from this or another system using a downloadable utility.
      • Download and extract the zip file to your WAS_HOME directory. From a command line, run isadc.[sh|bat] or launch index.html to use the web interface.

  2. Select the Runtime > JNDI Problem collector and click Start.

  3. Follow the prompts to automatically submit the collected data to IBM Support.

Collecting data manually

  1. Provide the version of WebSphere Application Server and interim fixes that have been installed. The version of WebSphere Application Server can be found using the following command:

    versioninfo

  2. 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? 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 and V6.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.

  10. Provide instructions to reproduce the problem.

  11. Follow instructions to send diagnostic information to IBM support.

For WebSphere Application Server V5.0 and V6.0 releases, collect the following additional information:

Note: You will need to specify the profile_root instead of install_root when using the following instructions for V6.0 releases.
  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.

    Notes:
    • Do not run this file directly from the bin directory or any other WebSphere directory.

    • Follow the instructions on Gathering information with 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 to send diagnostic information to IBM support.

If specific JNDI/Naming traces have been requested by the WebSphere Application Server support team, use the following instructions.

V6.0, 6.1, 7.0, 8.0 and 8.5 JNDI/Naming trace instructions:
  1. From the Administrative Console, select Servers > Application Servers > server_name > Change Log Details Levels.

  2. Remove any previous entries in the text field and type the following:

    Naming=all

  3. Apply and save changes.

  4. Select Servers > Application Servers > server_name > Diagnostic Trace Service.

  5. Change the Maximum Number of Historical Files to 10.

  6. Apply and save changes.

  7. Restart the sever and recreate the problem.

  8. Collect the following file:

    profile_root/logs/server_name/trace.log

    Note: If your trace rolls over (timestamp appended), send all files with the trace prefix.

  9. Follow instructions to send diagnostic information to IBM support.

V5.0 and 5.1 JNDI/Naming trace instructions:
  1. From the Administrative Console, select Servers > Application Servers > server_name > Diagnostic Trace Service.

  2. Specify the Trace Specification with the following:

    Naming=all=enabled

  3. Change the Maximum Number of Historical files to 10.

  4. Apply and save changes.

  5. Restart the sever and recreate the problem.

  6. Collect the following file:

    install_root/logs/server_name/trace.log

    Note: If your trace rolls over (timestamp appended), send all files with the trace prefix.

  7. Follow instructions to send diagnostic information to IBM support.

What to do next
Once you have collected the preceding information, you can simply submit the 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 for WebSphere Application Server
MustGather: Read first for WebSphere Application Server
Troubleshooting guide for WebSphere Application Server

Exchanging data with IBM Support

To diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:


Read first and related MustGathers


Cross reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server - Express Java SDK AIX, HP-UX, Linux, Solaris, Windows 8.5, 8.0, 7.0, 6.1, 6.0, 5.1
Application Servers Runtimes for Java Technology Java SDK

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Application Server
JNDI/Naming

Software version:

5.1, 6.0, 6.1, 7.0, 8.0, 8.5

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Software edition:

Base, Express, Network Deployment

Reference #:

1143296

Modified date:

2013-03-06

Translate my page

Machine Translation

Content navigation