On Thu, 26 Jul 2001, Matt Barre wrote:
> I guess it might help to include the trace from the out screen. :)
>
> Starting service Tomcat-Standalone
> Apache Tomcat/4.0-b6
> Starting service Tomcat-Apache
> Apache Tomcat/4.0-b6
> null
> java.lang.NullPointerException
> java.lang.NullPointerException
> at com.codestudio.management.PoolManConfiguration.parseXML(PoolManConfig
> uration.java:121)
> at com.codestudio.management.PoolManConfiguration.loadConfiguration(Pool
> ManConfiguration.java:75)
> at com.codestudio.management.PoolManBootstrap.<init>(PoolManBootstrap.ja
> va:61)
>
Well, the bug is inside the parseXML() method of PoolMan, so it's pretty
hard to tell what's going on. Where do you have the JAR file containing
PoolMan itself?
>
> Matt
>
Craig McClanahan
>
> ----- Original Message -----
> From: "Matt Barre" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, July 26, 2001 9:32 AM
> Subject: tomcat4b6 classpath for poolman.xml
>
>
> > I am moving a few of my applications from tomcat 3.2 to tomcat4-b6. I have them up
>and
> > running except for some trouble with poolman. From the trace before it kills
>tomcat, it
> > looks like it can't find the poolman.xml file. With tomcat 3.2 I simply have this
>file
> in
> > my jdkhome/jre/lib/ext/ folder. Anyone have a tip for where I should place a copy
>for
> > tomcat 4 to access? I'm on win2k with 2.0.4 of poolman.
> >
> > Thanks,
> > Matt
>
>
