Ok so think you have all the correct jars, latest version of dbforms and you are still getting a connection pool error. Well the tomcat list is full of them so please don't blame us -hahaha.
Why don't you send your server.xml, web.xml and servlet clips pertaining specifically to the dataSource you are trying to build. Also send the current error again. I really mean it if you look at the tomcat list, people stay on there with this same problem for a while. Shawn On Fri, 2003-01-24 at 01:45, McBrayer, Roy wrote: > I tried using the testsuite install. I moved my specific files into the > testsuite and additional jar files required but left the all of the original > testsuite jar files in place. I replaced the dbforms-config.xml with my xml > file and modified the web.xml slightly to meet my security requirements. I > get this error when trying to run from the testsuite directory. I still > get the same logging error from my original installation. > > 2003-01-23 10:35:38 StandardWrapperValve[jsp]: Servlet.service() for servlet > jsp threw exception > org.apache.jasper.JasperException: > org/apache/commons/pool/impl/GenericObjectPool > > javax.servlet.ServletException: > org/apache/commons/pool/impl/GenericObjectPool > at > org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp > l.java:533) > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 23, 2003 8:09 AM > To: McBrayer, Roy > Cc: [EMAIL PROTECTED] > Subject: RE: LogConfigurationException: No suitable Log constructor > > > Hi Roy, > > have you tried to get the new dbforms (1.1.3pr1) distro and to set up a new > and > clean web application from the examples directory WITHOUT try to use the new > > dbforms jar into an existant project ? > > I remember that: > > a) I downloaded the new 1.1.3pr1 distro > b) I set up the testsuite example web application from 0 using the original > war > archive, creating the new database using the provided scripts > c) I slightly modified the "dbforms-config.xml" and "log4j.properties" > config > files to point to my db and to setup the log4j appender > > and it worked (and it works) fine without problems ;^) > > Regards, > Luca > > > > > McBrayer, Roy wrote: > > I still get this error when running 1.1.3pr. I have all of the latest > > commons files in my lib directory and I have log4j.jar. I have been > unable > > to find much on this exception and have no idea what is causing it. It > > occurs whether or not I have a log4j.properties file present or not so it > > appears not to be related to the properties file. Does anyone have any > > ideas? > > > > Thanks, > > Roy > > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > DbForms Mailing List > > http://www.wap-force.net/dbforms -- shawn <[EMAIL PROTECTED]> ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
