The observed error can take the form of resources that do not get bound
into the jndi namespace (NameNotFoundException) or exceptions when
attempting to call methods on EMF objects. In the case of starting a
PortalServer the observered error was as follows:
2003.08.20 13:29:34.778 I com.ibm.wps.logging.LogManager init
Trace specification: *=all=disabled
.
2003.08.20 13:29:35.309 E com.ibm.wps.services.naming.NamingServiceImpl
lookup
SERV0006E: Cannot find object * in JNDI context *. - StackTrace
follows...
.
2003.08.20 13:29:35.309 E com.ibm.wps.services.naming.NamingServiceImpl
lookup
javax.naming.NameNotFoundException: jdbc/wps50DS. Root exception is
org.omg.CosNaming.NamingContextPackage.NotFound
at
com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.handleNameNotFound(WsnOpt
imizedNamingImpl.java:1999)
at
com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.getNextWsnOptimizedNaming
Context(WsnOptimizedNamingImpl.java:1316)
at
com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.getTargetContext(Ws
nOptimizedNamingImplBase.java:2409)
Prerequisites
Please download the UpdateInstaller below to install this fix.