NamingException

[Corey McGlone]

Hi folks,

I'm currently working on deploying my J2EE application to our development server. That server is running WebSphere, just like I am on my local box, but I'm getting an error when I try to access the database. Here's the error I'm getting:

javax.naming.NameNotFoundException: Context: localhost/nodes/localhost/servers/server34, name: jdbc/ds1: First component in name jdbc/ds1 not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL mg.org/CosNaming/NamingContext/NotFound:1.0

I get this error when the following line of code tries to execute:

context = new InitialContext();
myData = (DataSource)context.lookup("jdbc/ds1");   // This is where the exception is being thrown

So, I'm guessing that the datasource is not configured properly and that's what I'm going to investigate, but I wonder if anyone else could tell me what the problem is. Unfortunately, that exception doesn't mean a lot to me.

Thanks.

[Jeanne Boyarsky]

Corey,
The two main things to check are that you can see the datasource in the admin console and that you don't have any errors starting up your app.

[emm raha]

As Jeanne said, check the datasources using the admin console. A possible issue could be that you've created them in a node or cell or server instance that your application can't access.
[ December 28, 2004: Message edited by: emm raha ]

[Chris Staten]

I seem to be having a similar problem. I�m new to WSAD, but I did manage to get the admin console open. Now I don�t know how to check the datasources using it.

I�m getting the exact same error as Corey, so any help would be greatly appreciated.

-Thanks.

EDIT:

I googled this error out (and still ended up back at the ranch ) so I didn't realize that when I posted this question I was talking about WSAD and you guys were talking about Websphere the server. Sorry about that.

That being said, I'm still having a problem with the same error as what Corey posted.
[ January 19, 2005: Message edited by: Chris Staten ]

[Jeanne Boyarsky]

Chris,
It's actually a little easier to debug in WSAD. You don't need the admin console, just the test client.

In the server perspective, right click your server and select "universal test client." Then check under /jdbc whether your datasource is there.

[Chris Staten]

OK, I opened the universal test client, then went under the JNDI Explorer, and finally clicked on the jdbc link. I could see the datasource there, but when I used the JNDI Name lookup tool on the top of that screen I got the following error:

Could not perform lookup wit the JNDI name: context:

localhost/nodes/localhost/servers/server1, name: test_datasource: First component in the name test_datasource not found. 

Which, of course, is my error that I keep getting when I try to run my code. I was going to assume that it was my code that was causing this error, but now that I get it when using the Test Client I think it could be one of my datasource settings. Am I wrong in my reasoning?

On a side note, I�m new to WSAD and would love to get some kind of training with the program. I�ve looked at IBMs site and it looks like the class I should take is: course code WF331 �WebSphere Studio Application Developer V5 - Hands-on Overview �. Does anyone have any suggestions about this?

Thanks

[Jeanne Boyarsky]

Chris,
Since your datasource shows up in the tree, it is configured properly. That text box is only for looking up EJBs, so we should expect it to fail for a datasource.

What kind of module are you querying the JNDI from? Web, EJB, ...
Also, check you have created a resource reference from that project's deployment descriptor to the JNDI name of the datasource.

[Chris Staten]

Jeanne, I am querying from a Servlet, here is the code:

  
private void setConnectionParameters() throws javax.naming.NamingException {
Context ctx = null;
try{
String userID = getServletConfig().getInitParameter("uidOrcl");
String pwdOrcl = getServletConfig().getInitParameter("pwdOrcl");
String dataSource = getServletConfig().getInitParameter("dsNameOrcl");


Hashtable env = new Hashtable();
env.put(ctx.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");

ctx = new InitialContext(env);
System.out.println("made it here");//I see this in the command window.

DataSource ds = (DataSource) ctx.lookup(dataSource);//THIS IS WHERE THE CODE THROWS AN EXCEPTION.

ctx.close();

Dbconn conn = new Dbconn();
conn.setUserID(userID);
conn.setUserPWD(pwdOrcl);

} catch (NamingException e){
System.out.println("Exception Setting Datasources = " + e.toString());
throw new NamingException("TestSrvlLogon.setConnectionParameters NamingException: " + e.toString());
}
}

the init param "dsNameOrcl" from line six of the code above is set to "test_datasource" in the DD.


I also have the resource ref declared in the DD:

 
|resource-ref id="ResourceRef_1106261499518"|
|res-ref-name| jdbc/test_datasource |/res-ref-name|
|res-type| javax.sql.DataSource |/res-type|
|res-auth| Container |/res-auth|
|res-sharing-scope| Shareable |/res-sharing-scope|
|/resource-ref|

I could be completely flawed in my understanding of JDBC since I�m new to that as well as WSAD. Thank you so much for your help.




EDIT: I had to replace the angle brackets with pipes in the web.xml code because they didn't show up when I viewed the post.
[ January 21, 2005: Message edited by: Chris Staten ]

[Chris Staten]

OK, I�ve tried to break this back down to the most basic design that I can think so that debugging my problem will be easier on me. Here is a list of what I�ve done:

1. googled for tutorials on setting up datasources in WSAD and then retracing my steps to see if I missed anything. My settings look good to me (hrrrmmm, could be a problem with this statement )
2. I got rid of all my code except for the most necessary parts for making my connection and then debugging.
3. That�s it, nothing more!

Here is my Servlet code:

package my.test.package.testWork;
 
import java.text.*;
import java.util.*;
import javax.naming.*;
import javax.sql.*;
import java.io.*;
import javax.servlet.*;
import java.sql.*;
import oracle.jdbc.driver.*;
 
 
public class Test extends javax.servlet.http.HttpServlet {
 
 
public void doPost(
javax.servlet.http.HttpServletRequest request,
javax.servlet.http.HttpServletResponse response)throws IOException, ServletException {

DataSource ds = null;
Connection con = null;
PrintWriter out = response.getWriter();

response.setContentType("text/html");

try {
out.println("looking up the DataSource 
");
InitialContext ctx = new InitialContext();
ds = (DataSource) ctx.lookup("jdbc/test_datasource");
out.println("getting connection
");
con = ds.getConnection();
con.close();

} catch (Exception e) {
e.printStackTrace(out);

}
out.println("Done 
");


}
}

Here is a stack trace of my exception:

looking up the DataSource 
com.ibm.websphere.naming.CannotInstantiateObjectException: Exception
occurred while the JNDI NamingManager was processing a
javax.naming.Reference object. Root exception is java.lang.reflect.InvocationTargetException at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(CompiledCode))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at
com.ibm.ejs.j2c.J2CXAResourceFactory.createMCFEntry(J2CXAResourceFactory.java:375)
at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createMCFandPM(ConnectionFactoryBuilderImpl.java:1418)
at
com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1205)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
at
com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:873)
at
com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:680)
at
com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1712)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1567)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1480)
at
com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1187)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1067)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132) at
javax.naming.InitialContext.lookup(InitialContext.java:360) at
us.ms.state.deq.testWork.Test.doPost(Test.java:38) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:983)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:564)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200)
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:119)
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:276)
at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:618)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:439) at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672) Caused by:
java.lang.NoClassDefFoundError: oracle/jdbc/driver/OracleLog at
com.ibm.ws.rsadapter.spi.InternalOracleDataStoreHelper.setProperties(InternalOracleDataStoreHelper.java:101)
at com.ibm.ws.rsadapter.spi.WSRdbDataSource.(WSRdbDataSource.java:368) at
com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.setDataSourceProperties(WSManagedConnectionFactoryImpl.java:1049)
... 39 more Done

Any ideas?

-Thanks
[ January 24, 2005: Message edited by: Chris Staten ]

[Jeanne Boyarsky]

Chris,
Everything looks right to me. Maybe double check the database password? I got this kind of error once when I was locked out.

[Chris Staten]

Username and password are valid, I can log in under SQL Plus and Toad just fine. I�m really lost on this one. I�ve googled this out and found other people with this problem, just haven�t found the answer yet. If I ever figure out definitively what is causing this error, in my case, then I�ll post it here.