Caused By: Javax.naming.NameNotFoundException: Unable To Resolve 'jdbc.OpssDataSource'. Resolved 'jd

(Doc ID 2398150.1)

Last updated on JUNE 14, 2018

Applies to:

Oracle Application Access Controls Governor - Version 8.6.5 and later
Information in this document applies to any platform.

Goal

Q. Starting Weblogic, Deployed Application throws the below error

at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:254)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)
Caused By: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.OpssDataSource'. Resolved 'jdbc'; remaining name 'OpssDataSource'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1180)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:270)
at weblogic.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms