wood burning stoves 2.0*
The moose likes Websphere and the fly likes JNDI Connection Pool problem with WAS 5.0.2 and Teradata Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "JNDI Connection Pool problem with WAS 5.0.2 and Teradata" Watch "JNDI Connection Pool problem with WAS 5.0.2 and Teradata" New topic
Author

JNDI Connection Pool problem with WAS 5.0.2 and Teradata

eric mcentee
Ranch Hand

Joined: May 02, 2001
Posts: 66
Hello,
I am running into problems while trying to activate a JDBC connection pool on WAS 5.0.2. I am able to create the JDBC provider and Datasource. When I run the Test Connection tool, it comes back fine. However, when I try to run a sample application I get the following error:

***********************************
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R javax.naming.NameNotFoundException: Name comp/env/jdbc not found in context "java:".
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.naming.ipbase.NameSpace.getParentCtxInternal(NameSpace.java:1638)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal(NameSpace.java:997)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpace.java:920)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1211)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1203)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1257)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at javax.naming.InitialContext.lookup(InitialContext.java:359)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ncr.crm.util.TestConnPoolServlet.getConnection(TestConnPoolServlet.java:129)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ncr.crm.util.TestConnPoolServlet.getDate(TestConnPoolServlet.java:82)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ncr.crm.util.TestConnPoolServlet.service(TestConnPoolServlet.java:53)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:435)
[10/20/03 17:33:23:053 EDT] 1a8a1a10 SystemErr R at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)

***********************************
When I launch the Tivoli Performance viewer, I see the sample Cloudscape connection pools appear, by mine doesn't. When I run the dumpnamespace command I get the following:

***********************************
58 (top)/nodes/WUSEM180000-OAT/servers/server1/jdbc/NCRCRMDB
58 ERROR: Could not instantiate a bound object.
58 Bound Java type: NCRCRMDB
58 Local Java type: NULL
58 String representation:
************************************
There are no errors in the log files, and as I've mentioned, the test connection passes.
Any ideas on what might prevent this? I should add that the JDBC driver is for Teradata, so when I create a JDBC Provider in the Admin Console I have to select "com.ibm.websphere.rsadapter.GenericDataStoreHelper" when creating the Datasource under the Datasource Helper Classname.

Thank you in advance for your help,
Eric McEntee
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JNDI Connection Pool problem with WAS 5.0.2 and Teradata
 
Similar Threads
naming error in websphere datasource
WSAD DataSource Connection Exception
Connection Pooling and JDBC lookup.
Naming Not Found Exception
Resource Reference JNDI lookup failure...Urgent