Duncan, I believe (and could be wrong) that this is intended behaviour. The work directory is like Tomcat's cache of all the webapps it is currently serving. When a request comes in for a page it tries to serve from this directory, if the class file does not exist it generates the .java files from /webapp and then compiles them so that it can serve them.
So, the 3s delay and 100% utilisation is expected because Tomcat is recompiling the files so that it can serve them. PJ On Fri, 2004-03-26 at 18:39, Duncan Krebs wrote: > Hi, > I have had this snag for some time now and its starting to get the best of me. I'm > running tomcat 4.1 and when I manually remove the .java and .class files in the > /work/standalone folder even after the initial request of recompiling the jsp's > tomcat hits 100% on my CPU and the overall response time is delayed by about 3 > seconds on each request. > > As I deleted different sub folders in the work folder (all within the same web > application) the degraded performance was consistent with the different sub folders > that I was deleting even after the pages were recompiled. Has anyone experienced > this before? > > All of my requests are going through a Servlet controller and I have a lot of > classes in my WEB-INF folder that are part of the framework but I don't think that > would have anything to do with this. I've also tried rebuilding my entire project > from scratch and I'm still having the same issue of a slowed response time of about > 3 seconds and tomcat taking all my CPU. > > Regards, > dkrebs > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
