Weblogic javax.naming.NameNotFoundException while running application

Question

I have created a data source name in Weblogic 10.3.6 as jdbc/appsmDS and the same name has been given in application to lookup.

However when I am trying to run application, I am getting the following error

javax.naming.NameNotFoundException: While trying to lookup 'jdbc/appsmDS' 
didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/appsmDS'

How can I resolve this issue?

@Satya with `java:jdbc/appsmDS` I was able to run application, so it has to be `java:jdbc/appsmDS`? — Jacob, May 08 '13 at 12:40
yes , when looking up the full JNDI structure maps to java:jdbc/appsmsDS. Posting all of it as answer kindly accept — Satya, May 08 '13 at 12:43
@Satya Kindly post as an answer I will be glad to accept it. — Jacob, May 08 '13 at 12:43
Plese see my answer also http://stackoverflow.com/a/36981908/3506427 . My problem was that the local sql server service was stopped. — bogdan.rusu, May 02 '16 at 12:00

score 5 · Answer 1 · edited Jan 07 '20 at 16:55

5

The problem in this case is probably that the datasource is not deployed in the "server" inside weblogic domain.

edited Jan 07 '20 at 16:55

Brad Larson

170,088
45
397
571

answered Aug 18 '15 at 20:37

Rodrigo Klein

59
1
3

2

I'm sorry but that link doesn't seem to point to the right post. – nicolimo86 Feb 10 '17 at 10:35

score 3 · Accepted Answer · answered May 08 '13 at 12:43

3

when looking up the DS the full JNDI structure maps to java:jdbc/appsmsDS.

Please use it for lookup.

answered May 08 '13 at 12:43

Satya

8,693
5
34
55

score 2 · Answer 3 · edited May 21 '15 at 19:29

2

This exception happens when the property provider.url is pointing at the AdminServer (localhost:7001, in my case) and JDBC is not installed.

You may have other instances where it is installed, check your JNDI TREE to verify this.

Greetings, JFM

edited May 21 '15 at 19:29

vakata

3,726
1
17
31

answered May 21 '15 at 19:00

Joas Flores

21
1

score 1 · Answer 4 · edited Jan 17 '14 at 10:39

1

javax.naming.NameNotFoundException: This will generally occur if any of the xml files like ejb-jar.xml and weblogic-ejbjar.xml are missing in the ear file deployed. The only workaround is to generate a fresh ear file with all the xml files included.

edited Jan 17 '14 at 10:39

Mani

17,549
13
79
100

answered Jan 17 '14 at 10:19

user2858116

11
1

score 0 · Answer 5 · answered Oct 01 '19 at 12:06

0

Make sure you have clicked on the "Activate Changes" button on the left top corner and also check your xxxxxxDataSource-nnnn-jdbc.xml file is created under config/jdbc directory.

answered Oct 01 '19 at 12:06

Pratap Kumar Panda

131
1
7

Weblogic javax.naming.NameNotFoundException while running application

5 Answers5

Linked