IBM Support

MustGather: JNDI and Naming problems in WebSphere Application Server

Troubleshooting


Problem

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.

  • Read First and Related MustGathers
  • JNDI Naming Mustgather Information
    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.sh
    2. Is this a Base or Network Deployment installation of WebSphere Application Server?
    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...
    5. Is WebSphere Application Server Security enabled (Security > Global Security > Enable Application Security)?
    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, or other client)?
      • If it is other client, please specify what type of client.
    8. Provide a code sample that shows the InitialContext and lookup statement.
      • Include the PROVIDER_URL and INITIAL_CONTEXT_FACTORY as set either in code, Java virtual machine (JVM) setting, and/or a 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 IBM Docs for details about invocation details.
      • Note that in all releases of WebSphere Application Server, each server, node agent, and 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. For java:comp/env problems, use the NameServer MBean to dump the java: namespace.
    11. Provide instructions to reproduce the problem.
    12. Follow instructions to send diagnostic information to IBM support.
  • Collect Configuration Data and Logs
    1. Delete or rename the logs in the profile_root/logs directory.
      • If you are running the deployment manager, also delete the logs in the profile_root_dmgr/logs directory.
    2. Start the deployment manager (if applicable), the node agent (if applicable), and the Application Server.
    3. Recreate the problem.
      • We recommend documenting the approximate system time that the problem occurs.
    4. Run the profile_root/bin/collector.sh or the collector.bat command.
      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 IBM Documentation.
      • Do not use the summary option.
    5. If you are running with a Deployment Manager (Network Deployment installation of WebSphere Application Server), run the profile_root_dmgr/bin/collector.sh or collector.bat command again (this time against the deployment manager) using the same instructions as in step 4.
    6. Follow instructions to send diagnostic information to IBM support.
  • Enable Tracing
    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: 
      *=info:Naming=all
    3. Apply (or press OK) 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 (or press OK) and save changes
    7. Restart the server 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 historical files with the trace prefix.
    9. Follow instructions to send diagnostic information to IBM support.
  • 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:
    • Service Request (SR)
    • E-mail
    • FTP to the Enhanced Customer Data Repository (ECuRep)

    Instructions for exchanging information with 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

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"ARM Category":[{"code":"a8m50000000CdN3AAK","label":"WebSphere Application Server traditional-All Platforms-\u003EORB-Naming-\u003EJNDI Naming"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.5;9.0.5"},{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7JFU","label":"WebSphere Application Server - Express"},"ARM Category":[{"code":"a8m50000000CdN3AAK","label":"WebSphere Application Server traditional-All Platforms-\u003EORB-Naming-\u003EJNDI Naming"}],"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.5"},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":null,"Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
28 December 2023

UID

swg21143296

Page Feedback