My Oracle Support Banner

Unable to Resolve JNDI Lookup for Datasource to Connect to the Database from a Portlet Deployed in WC_Portlet Managed Server : javax.naming.NameNotFoundException (Doc ID 1316402.1)

Last updated on JUNE 17, 2024

Applies to:

Oracle WebCenter Portal - Version 11.1.1.4.0 and later
Oracle WebCenter Portal for OCI - Version 12.2.1.4_24.2 and later
Information in this document applies to any platform.
 

Symptoms

When attempting to connect to the database using a data source from a portlet deployed to the WC_Portlet container, the portlet can't connect to the database.
This same application works when deployed to the JDeveloper IntegratedWebLogicServer.


The WC_Portlet.out shows the following error:


<Apr 12, 2011 11:41:37 AM EDT> <Warning> <org.apache.myfaces.trinidadinternal.skin.SkinFactoryImpl> <BEA-000000> <Can't find a skin that matches family fusionFx and renderkit portlet, so we will use the simple skin>
in getConnection method
javax.naming.NameNotFoundException: Unable to resolve 'jdbc.ABC_DS'. Resolved 'jdbc' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'jdbc.ABC_DS'. Resolved 'jdbc']; remaining name 'ABC_DS'
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1034_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
...


Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.ABC_DS'. Resolved 'jdbc'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)



Steps To Reproduce:

The issue can be reproduced with the following steps:

  1. Create a Producer with a Portlet that connects to the database using a Data Source.
    For example:


    Where server is the server name where the WebCenter domain is running.

  2. Call the Portlet from WebCenter Spaces or a custom WebCenter consumer application.
    You will see the Portlet can't connect to the database.

    The WC_Portlet.out file should show the error mentioned above.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.