[FIXED] javax.naming.NameNotFoundException: Unable to resolve 'MyDB'. Resolved '' Weblogic 12.1.3. c

Issue

While migrating from Tomcat to Weblogic 12.1.3 I got this exception javax.naming.namenotfoundexception while trying to look up then I have tried the following : href="https://stackoverflow.com/questions/21355945/namenotfoundexception-while-trying-to-lookup-jdbc-only-when-publishing-from-e">NameNotFoundException: While trying to lookup 'jdbc' only when publishing from Eclipse Kepler but not Indigo and How to access JNDI data source defined in weblogic 10.3.6

I got the in titled error now

My lookup code

ds = (DataSource) initContext.lookup("MyDB");

in weblogic JNDI Name

MyDB

Any help please?

Solution

Unlike Tomcat, weblogic creates multiple servers (Usually an Admin Server, plus at least one other). Each server has to be allocated the data source. In a clustered environment, you need to apply the datasource to the cluster servers.

1. Log into the Weblogic console, and check the datasource JNDI name (don't confuse this with the datasource name, which is purely to keep the console listing looking pretty). The JNDI name should be something like jdbc/MyDB
2. Check the datasource Targets tab, and make sure it is applied to the server/cluster you are going to deploy your web app to.
3. Restart Weblogic. I find that data sources sometimes need this before they become visible to application code.
4. Deploy your web app to the correct server/cluster.

You should be to connect to the datasource as normal. I always use a Spring JNDI bean, so I can't help with the exact syntax. The suggestions by @Maas look good.

Answered By - kiwiron
Answer Checked By - Mary Flores (JavaFixing Volunteer)