"Javax.naming.NameNotFoundException: While Trying To Lookup 'jdbc.intersys/nmsadmin'" When Starting NMS Managed Server
(Doc ID 2456825.1)
Last updated on AUGUST 04, 2022
Applies to:
Oracle Utilities Network Management System - Version 2.3.0.0.0 and laterOracle Network Management for Utilities - DMS - Version 2.3.0.0.0 and later
Information in this document applies to any platform.
Symptoms
On : 2.3.0.0.0 version, Java Application Server
Attempting to start the NMS managed server results in this error:
2018-10-04 19:53:15,866 WARN ejb.DataSourceHelper:291 - While trying to lookup 'jdbc.intersys/nmsadmin' didn't find subcontext 'jdbc'. Resolved ''
javax.naming.NameNotFoundException: While trying to lookup 'jdbc.intersys/nmsadmin' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/intersys/nmsadmin'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1224)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:268)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:217)
at weblogic.jndi.internal.BasicNamingNode.lookupIgnorePartition(BasicNamingNode.java:1503)
at weblogic.jndi.internal.PartitionHandler.lookupSharable(PartitionHandler.java:88)
at weblogic.jndi.internal.ServerNamingNode.lookup(ServerNamingNode.java:584)
at weblogic.jndi.internal.RootNamingNode.lookup(RootNamingNode.java:81)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:307)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:430)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
The JDBC datasources were created according to the instructions
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |