Yes! I had misspelled the package for my driver, but once I corrected that it works! Well, it seems to work.
Thanks Again! Eddie ----- Original Message ----- From: "Bryan Field-Elliot" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Thursday, March 07, 2002 5:05 PM Subject: Re: [Off Topic] Poolman Setup > I'm no expert (having just picked up poolman a week ago) but, it appears > to me that you don't have poolman.xml in the right place. It needs to be > in either of the following places: > > 1. In the WEB-INF/classes directory (this is what I do) > 2. Jar'd up, and then put the Jar in the WEB-INF/lib directory (as > opposed to what you tried, which is putting the un-jar'd XML file in the > lib directory). > > Bryan > > On Thu, 2002-03-07 at 15:47, Eddie Bush wrote: > > I've done everything (I think) that poolman requires in order to function, and yet it does not. After placing only the required jars into my \lib folder, and having no success with Poolman starting, I threw all of them in. It still doesn't work. > > I wasn't at all sure, from the documentation, where I should poke the poolman.xml file. Initially I had it in my WEB-INF directory. Then, I copied it to the \lib directory. Still no luck. > > Every time Poolman is started, I get the same exact error - a null pointer exception. This occurs when poolman is calling parseXML from loadConfiguration. The relevant piece of the stacktrace is: > > java.lang.NullPointerException > at com.codestudio.management.PoolManConfiguration.parseXML (PoolManConfiguration.java:121) > at com.codestudio.management.PoolManConfiguration.loadConfiguration (PoolManConfiguration.java:75) > at com.codestudio.management.PoolManBootstrap.<init> (PoolManBootstrap.java:61) > at com.codestudio.management.PoolManBootstrap.<init> (PoolManBootstrap.java:54) > at com.codestudio.sql.PoolMan.start (PoolMan.java:97) > > The rest of the stacktrace goes into my servlet - which worked fine before I tried to kick off Poolman in it's init method. > > I have also tried not calling start, but, instead, just allowing Poolman to do it's 'lazy' initialization - same exact result. > > I would be most appreciative if someone out there could give me a 'heads up'. > > I'm running Tomcat 4.0.1 (I can't see why that would matter) and JDK 1.3. > > Thanks! > > Eddie > > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
