NameNotFoundException after creating a work manager programmatically
 Technote (troubleshooting)
 
Problem(Abstract)
You create a work manager using java/ jmx (programmatically), then use the WebSphere® Application Server Administrative Console to verify that it exists; however, performing a Java Naming and Directory Interface™ (JNDI) lookup fails with javax.naming.NameNotFoundException.

When you restart the Application Server, everything works fine and the JNDI lookup is now successful. Now if you delete the work manager from the Administrative Console, recreate it programmatically, and everything works fine.
 
Cause
The naming information is cached.
 
Resolving the problem
When creating work managers programmatically you must restart the Application Server to pick up the changes. This is by design; however, a feature has been submitted to request the design be modified in a future release.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
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: 5.0
Software edition:
Reference #: 1162530
IBM Group: Software Group
Modified date: Mar 5, 2004