Learning more about JNDI and naming
 Technote (FAQ)
 
Problem
Learning more about Java™ Naming and Directory Interface (JNDI) is the first step in the troubleshooting process. This document provides you with educational information that can help you learn more about this topic.
 
Solution

1. Learning more 2. Troubleshooting 3. Collecting data

Getting background information on JNDI and naming
In WebSphere® Application Server V5.0 and later, the namespace is broken up from one large name space to a namespace for each JVM. See logical view.

The most common problem resulting in a NameNotFoundException is when the initial context has bootstrapped to the wrong server/namespace. Remember that each application server, node agent, and deployment manager has it's own namespace.

Ensure the bootstrap port for the server you are binding to is specified. The bootstrap port can be seen in the serverindex.xml as well as in the administrative console.

If no port is specified, port 2809 is used as a default. This is the default port for the Node Agent and will not have application or resource objects in its namespace.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server - Express AIX, HP-UX, Linux, Solaris, Windows 6.0, 5.1, 5.0
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > JNDI/Naming
Operating system(s): Windows
Software version: 6.0
Software edition:
Reference #: 1243575
IBM Group: Software Group
Modified date: Aug 14, 2006