EOF javax.naming.NameNotFoundException problem
EOF javax.naming.NameNotFoundException problem
- Subject: EOF javax.naming.NameNotFoundException problem
- From: Dov Rosenberg <email@hidden>
- Date: Fri, 12 Nov 2004 17:20:08 -0500
Title: EOF javax.naming.NameNotFoundException problem
I have noticed since 5.2 that our WO apps we deploy as servlets throw 2 exceptions (the same exception twice) at startup but after the app starts it seems to run fine. If we run our app as a WO application in Eclipse or from the command line (not as a servlet) the exceptions don’t happen.
It looks like the JDBCContext class is trying to connect to the servlet engine to look up the database information using JNDI. The setupJndiConfiguration method in JBDCContext looks for a key in the ConnectionDictionary called DataSourceJndiName. I added the key, but now the app doesn’t load due to a classcast exception. I set up the JNDI resource in Tomcat properly with a resource name = wo/dsmapping/MyModel. The naming exception is no longer thrown but the app also fails.
<TagLibrary>[2004-11-12 10:06:40 EST] <main> javax.naming.NameNotFoundException: Name jdbc is not bound in this Context
at org.apache.naming.NamingContext.list(NamingContext.java:389)
at org.apache.naming.NamingContext.list(NamingContext.java:397)
at org.apache.naming.NamingContext.list(NamingContext.java:397)
at org.apache.naming.NamingContext.list(NamingContext.java:412)
at org.apache.naming.SelectorContext.list(SelectorContext.java:353)
at javax.naming.InitialContext.list(InitialContext.java:387)
at com.webobjects.jdbcadaptor.JDBCContext.setupJndiConfiguration(JDBCContext.java:279)
at com.webobjects.jdbcadaptor.JDBCContext.connect(JDBCContext.java:165)
at com.webobjects.jdbcadaptor.JDBCContext._tryConnect(JDBCContext.java:331)
at com.webobjects.jdbcadaptor.JDBCContext._fetchJDBCInfo(JDBCContext.java:558)
at com.webobjects.jdbcadaptor.JDBCPlugIn.jdbcInfo(JDBCPlugIn.java:862)
Question: It appears that something changed from 5.1, to 5.2 regarding making the connection as far a servlets go. It would be great if I could configure a JDBC Connection pool managed by the servlet container. But I get the impression that either I am doing something wrong in setting up the servlet JDBC resource or WO’s implementation of talking to a JNDI provider is messed up. In 5.1 this exception was not thrown. Hopefully 5.3 will make this problem go away again. It is more of an annoyance than a problem at this point, I am just trying to get it cleaned out of our log files.
If anyone has any suggestions I am willing to listen.
--
Dov Rosenberg
Conviveon Corporation
http://www.conviveon.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden