have you tried handling it this way? 1. compile the jsp on a staging server 2. tar up the files 3. upload to the production servers 4. untar 5. touch jsp files 6. touch compiled classes in the working directory
I used that approach in the past to handle updates to the production servers. peter ----- Original Message ----- From: Dale, Matt <[EMAIL PROTECTED]> Date: Fri, 2 Jul 2004 14:49:21 +0100 Subject: JSP updates leading to OutOfMemoryErrors and Tomcat Crashes To: "Tomcat Users List (E-mail)" <[EMAIL PROTECTED]> We have a webapp that consists of >1000 jsps that are code generated from another application. What we are experiencing is within an hour or two of uploading some updated jsps OutOfMemoryErrors start happening and Tomcat crashes. Once restarted, it seems fine and survives until we next do an update when once again after a couple of hours the same problems reoccur. We tried forking the Jsp compliation, but this hasn't resolved the problem. I was wondering if anybody has ever come accross similar behaviour and if there are any known issues that may relate to it. Ta Matt InterScan_Disclaimer.txt - 1K Download noname - 1K Download --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
