> -----Original Message----- > From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] > Sent: Wednesday, November 17, 2010 06:46 PM > To: Tomcat Users List > Subject: RE: FW: After manager says that there was a leak, how to use a > profiler? > > > From: Brian [mailto:bbprefix-m...@yahoo.com] > > Subject: RE: FW: After manager says that there was a leak, how to use a > profiler? > > > It seems that the JARs inside "...WEB-INF/lib" are not being > > discovered or used. > > Hence the request to see your catalina.properties - which looks fine. What's > in the <Context> elements for your webapps? If you're using anything other > than the default (and implicit) <Loader>, that might affect how class searching > is done. Also, if you have anything in the system classpath at Tomcat startup, > that might also impact proceedings.
Inside the <Context> there is nothing non-standard. Nothing about the loader indeed. It doesn't work either in the Tomcat installation at my production server, or the Tomcat local installation that my Eclipse uses when running the app. One interesting thing is happening though. Now it is showing the error messages in the log when I run it on Eclipse, but then IT WORKS! This is the context that Eclipse generated for the app, that shows all the error messages in the log: <?xml version="1.0" encoding="UTF-8" ?> <Context docBase="C:\Tomcat\webapps\VistaControlador" reloadable="true" source="org.eclipse.jst.jee.server:VistaControlador" /> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org