|
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
- 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 and V6, this can be found using the
versioninfo command.
- For all releases of V5 or V6, is this a base or Network Deployment
installation?
- If an exception has occurred, provide the full stack trace or the log
file in which it is contained.
- What is the network topology or system environment? How many nodes?
Please supply a topology map or describe the topology in words.
- Is WebSphere Application Server Security enabled?
- Is the client local or remote to the server? If a remote server is
involved, is there firewall present?
- What type of client is being used (J2EE™ Application, Thin Client,
Thick Client, EJB™)?
- 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.
- 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. In all releases of V4.0, the name server runs on the
administrative server.
- Provide instructions to reproduce the problem.
- Follow instructions to send
diagnostic information to IBM support.
For V4.0, 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 instructions below on V6.0
- 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.
- Start the deployment manager (if applicable), the node agent (if
applicable), and the Application Server.
- Recreate the problem. Write down the approximate system time that the
problem occurs.
- 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.
- 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.
- Follow instructions to send
diagnostic information to IBM support.
If specific JNDI/Naming traces have been requested by the WebSphere
support team, use the following instructions:
V6.0 JNDI/Naming Trace Instructions
- From the Administrative Console, select Servers -> Application
Servers -> server_name -> Change Log Details
Levels
- Remove any previous entries in the text field type the following:
- Apply and save changes.
- Select Servers -> Application Servers ->
server_name -> Diagnostic Trace Service
- Change the Maximum Number of Historical Files to 10.
- Apply and save changes.
- Restart the sever and recreate the problem.
- Collect the following file:
<PROFILE_ROOT>/logs/<server_name>/trace.log |
Note: If your trace rolls over (timestamp appended), please send
all files with the trace prefix
|
- Follow instructions to send
diagnostic information to IBM support.
V5.0 and V5.1 JNDI/Naming Trace Instructions
- From the Administrative Console, select Servers -> Application
Servers -> server_name -> Diagnostic Trace
Service
- Specify the Trace Specification with the following:
- Change the Maximum Number of Historical files to 10.
- Apply and save changes.
- Restart the sever and recreate the problem.
- Collect the following file:
<WebSphere Application
Server_root>/logs/<server_name>/trace.log |
Note: If your trace rolls over (timestamp appended), please send
all files with the trace prefix
|
- Follow instructions to send
diagnostic information to IBM support.
V4.0 Administrative Server JNDI/Naming Trace Instructions
- Make a backup copy of the <WebSphere Application
Server_root>/bin/admin.config file.
- Open the <WebSphere Application Server_root>/bin/admin.config
file.
- Add or update the following lines:
com.ibm.ejs.sm.adminServer.traceString=com.ibm.ejs.ns.*=all=enabled:com.ibm.ws.naming.*=all=enabled:com.ibm.websphere.naming.*=all=enabled
com.ibm.ejs.sm.adminServer.traceOutput=<fully_qualified_pathname> |
The following is an example of <fully_qualified_pathname>:
|
/opt/WebSphere/AppServer/logs/admintrace.log |
|
- Restart the Administrative Server and recreate the problem.
- Collect the following file:
/opt/WebSphere/AppServer/logs/admintrace.log |
|
- Follow instructions to send
diagnostic information to IBM support.
V4.0 Application Server JNDI/Naming Trace Instructions
- Run the Administrative Console, expand the topology frame and
highlight the application server which is going to be traced to display
its properties, and click on the Services tab.
- Click on Trace Service in the services table, and click Edit
Properties.
- Put the following in the Trace Specification field:
com.ibm.ejs.ns.*=all=enabled:com.ibm.ws.naming.*=all=enabled:com.ibm.websphere.naming.*=all=enabled |
|
- Select the Specify radio button and type the fully qualified pathname
to where the trace should be output
|
<WebSphere Application
Server_root>/logs/apptrace.log |
|
- Click OK and then click Apply.
- Restart the Application Server and recreate the problem.
- Collect the following file:
<WebSphere Application
Server_root>/logs/apptrace.log |
|
- Follow instructions to send
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. |
|
|