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

Question

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 : 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?

@Maas i just did and i got While trying to look up comp/env/jdbc/MyDB remaining name 'comp/env/jdbc/MyDB — Dunken, Aug 12 '14 at 08:00
Sorry, couldn't understand your comment. Do you mean even after using "java:comp/env/jdbc/MyDB" you got NameNotFound? — Maas, Aug 12 '14 at 08:03
@Maas yes i got javax.naming.NameNotFoundException: While trying to look up comp/env/MyDB — Dunken, Aug 12 '14 at 08:06
See if this thread helps: https://community.jboss.org/message/251298 — Maas, Aug 12 '14 at 08:09
Hmmm, may be... lets wait for other experts to add their comments — Maas, Aug 12 '14 at 08:27

score 35 · Accepted Answer · answered Aug 12 '14 at 10:50

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.

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
Check the datasource Targets tab, and make sure it is applied to the server/cluster you are going to deploy your web app to.
Restart Weblogic. I find that data sources sometimes need this before they become visible to application code.
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.

I found AdminServer must be checked on Targets tab. That was not intuitive to me when I configured Weblogic. — CodeChops, Apr 27 '15 at 16:16
Man we wasted hours on this here. The AdminServer indeed must be checked. Thanks CodeChops. — Ronen Festinger, Aug 26 '15 at 22:34
I had to check AdminServer and also update the JNDI name from myDB to jdbc/myDB. Thanks for your help. — Sammy Cakes, Jan 24 '20 at 15:08

score 3 · Answer 2 · answered Aug 05 '15 at 12:49

3

Restarting the server after deployment helps.

answered Aug 05 '15 at 12:49

ACV

9,964
5
76
81

score 2 · Answer 3 · answered Oct 05 '16 at 15:14

Check the JNDI case (MyDB != MyDb). It sounds trivial, but it happened to me and had a hard time spotting it. Since this is the first thread google returns when searching for this issue, I post it here in case it helps.

Besides that, @kiwiron 's answer covers everything else.

score 0 · Answer 4 · answered Apr 03 '18 at 01:34

0

For me, starting the managed server from Windows command line instead of starting it using the WebLogic Admin console solved the javax.naming.NameNotFoundException problem. Not sure why this was the case though.

answered Apr 03 '18 at 01:34

weiwei

21
2

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

4 Answers4

Linked