Howdy, >The fact that in the stock distribution the fork attrribute is set to >false by default is IMHO not very good choice. Took me several days of >headaches trying to find the leak in my code. When there is a disign >choice "slow" versus "crash for 1% of users" I would choose slow and put >into some doc how to make it faster if it is required.
Well, that's your opinion. ;) I for one disagree. In addition, this issue is well-documented in several places, including the JSPs How-To (http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jasper-howto.html), the Release Notes, the JSP servlet in $CATALINA_HOME/conf/web.xml, this mailing list's archives, and links to this mailing list's archives from the tomcat FAQ Memory page. Workarounds such as precompilingare also documented in at least one of the above places, including pre-compiling your JSPs. >and following bash script: >while [ 1 ] >do > /usr/bin/lynx -dump http://localhost:8080/test.jsp >> /tmp/m.txt > touch /usr/local/jakarta-tomcat-4.1.29/webapps/ROOT/test.jsp If this (the JSP page source changing on every user request) is a realistic scenario for your webapp, you will also run into other, deeper performance- and data-integrity related issues. But why do I get the feeling the above script doesn't mimic any realistic production system scenario? ;) 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]
