Simple solution, don't use the LE version. Use the full version. Your problems will disappear.
> -----Original Message----- > From: Gregg Bolinger [mailto:[EMAIL PROTECTED] > Sent: Monday, August 04, 2003 2:07 PM > To: 'Tomcat Users List' > Subject: RE: Connection Pooling HELP > > > I found out you also need the commom-pool.jar file also. Why does > Tomcat provide Connection Pooling but doesn't distribute all necessary > files to do so with the Binary release? These 2 jar files are not > specific to the database, so you would think Tomcat would come with > them. Not to mention Tomcats docs don't mention the fact > that you need > to download them. GRRRR! > > Gregg > > -----Original Message----- > From: Gregg Bolinger [mailto:[EMAIL PROTECTED] > Sent: Monday, August 04, 2003 12:45 PM > To: 'Tomcat Users List'; 'Tomcat Users List' > Subject: RE: Connection Pooling HELP > > You might be right. I don't have the commons-dbpc.jar file. > Why isn't > this included with the Binary release of Tomcat and where can > I get it? > I can't find it with all the other Commons downloads. > > Thanks > > Gregg > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Monday, August 04, 2003 12:40 PM > To: Tomcat Users List > Subject: Re: Connection Pooling HELP > > Gregg Bolinger wrote: > > > I am trying to get connection pooling working with Tomcat 4.1.24-LE. > > Below is some relevant code. Tomcat starts up just fine. > I have all > my > > JAR files I need in the right place. If I create my own connection > > using JDBC it all works just fine. But using a connection pool is > > failing. The error message is after all the code. > [...] > > >And I get this error message > >javax.naming.NamingException: Cannot create resource instance > > at > >org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceF > >actory.java:189) > > at > >javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:3 > >01) > > at > >org.apache.naming.NamingContext.lookup(NamingContext.java:834) > > at > >org.apache.naming.NamingContext.lookup(NamingContext.java:181) > > at > >org.apache.naming.NamingContext.lookup(NamingContext.java:822) > > at > >org.apache.naming.NamingContext.lookup(NamingContext.java:181) > > at > >org.apache.naming.NamingContext.lookup(NamingContext.java:822) > > at > >org.apache.naming.NamingContext.lookup(NamingContext.java:181) > > at > >org.apache.naming.NamingContext.lookup(NamingContext.java:822) > > at > >org.apache.naming.NamingContext.lookup(NamingContext.java:194) > > at > >org.apache.naming.SelectorContext.lookup(SelectorContext.java:183) > > at > javax.naming.InitialContext.lookup(InitialContext.java:347) > > at AddReference.processRequest(AddReference.java:65) > > at AddReference.doPost(AddReference.java:115) > > at > javax.servlet.http.HttpServlet.service(HttpServlet.java:760) > > at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > > > This may not help, but I have heard of this happening when some needed > .jars were missing from CATALINA_HOME/common/lib - in particular, > commons-dbcp.jar and commons-pool.jar. > > -- > Lynn Hollerman. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
