Howdy, >Hello! We're running Tomcat 4.0.4 behind Apache 1.3.27 on Linux using >mod_jk. I've noticed really long startup times for Tomcat on our system, >even though we already have the ROOT.war uncompressed. During this time, >all the user can see is an Internal Server Error page until Tomcat is >ready. >Note the time is worse for the initial access after we deploy a new ROOT >directory than on subsequent restarts (probably because we have some pages >compiled already?). Is there any way to reduce this wait time? Sometimes it >can be on the order of a minute or more, which isn't very good for our >users.
1. Compressing or uncompressing WARs doesn't make much of a difference unless they're huge. 2. Make sure you don't start anything you don't need, i.e. comment out any connectors, valves, loggers, engines, hosts, contexts you don't use from server.xml. 3. Remove any webapps you don't need. 4. See if the server's startup time is also slow when you take out your struts webapp. 5. Take apache and the apache->tomcat connectors out of the equation temporarily: just start up tomcat and see how long that takes. Personally, I haven't benchmarked tomcat 4.0.x in a while but 4.1.29 starts in about 15sec for me with one connector, one valve, one webapp, normal loggers. EMC ;) I did a co-op there during my undergrad and still know several of the engineers... Nice place. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
