My experience with poolman.jar and TC 4 suggests you put the poolman.xml file in the classes folder under $CATALINA_HOME. Actually how I did it since I disliked having poolman.xml sitting in the classes folder was to put in the conf folder and sym link to it from the classes folder. That way it sits where I think it belongs and poolman.jar still sees it. The sym link idea may not work if you're on a different platform (ie Windows) though.
--David Smith On Monday 19 November 2001 05:08 am, you wrote: > Hi all, > > I'm running Tomcat 4.01 on Redhat 7.2 installed on an intel box. > > What I need to know is this: - I have recently moved a Servlet from another > machine running tomcat 3.2.3. (Redhat 7.1) > > Tomcat 3.2.3 directory structure is as below, the servlet works without any > issues. > > $TOMCAT_HOME/lib/ - ... > - com.opal.isp.generic.jar > - poolman.jar > - poolman.xml > > $TOMCAT_HOME/webapps/server/ - build.xml > WEB-INF/ - web.xml > - lib/ - >com.opal.isp.logginserver.jar - jar file containing the > servlet package > META-INF/ > > Under tomcat 4 > > The directory is duplicated and the server wide libraries are put into the > /lib directory. tomcat4 throws the following and causes the tomcat to stop. > > java.lang.NullPointerException > java.lang.NullPointerException > at > com.codestudio.management.PoolManConfiguration.parseXML(PoolManConfiguratio >n.java:121) at > com.codestudio.management.PoolManConfiguration.loadConfiguration(PoolManCon >figuration.java:75) at > com.codestudio.management.PoolManBootstrap.<init>(PoolManBootstrap.java:61) > at com.codestudio.util.SQLManager.assertLoaded(SQLManager.java:109) at > com.codestudio.util.SQLManager.requestConnection(SQLManager.java:190) at > com.codestudio.sql.PoolMan.connect(PoolMan.java:184) > at java.sql.DriverManager.getConnection(DriverManager.java:517) > at java.sql.DriverManager.getConnection(DriverManager.java:177) > at com.opal.isp.db.DBManager.connect(DBManager.java:47) > at com.opal.isp.db.DBManager.executeSelectQuery(DBManager.java:69) > at com.opal.isp.logging.Updater.updateCUST(Updater.java:207) > at com.opal.isp.logging.Updater.refresh(Updater.java:65) > at com.opal.isp.logging.Updater.run(Updater.java:41) > > This indicates that the config file couldn't be found. > > QUESTION: Can anyone suggest a reason as to why this is happening, even > tho this works under 3.2.3 ? QUESTION: What would I need to do to make > poolman.xml visible to all webapps ? > > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
