hi,
I think I am correct when I say javac is only used by tomcat compile jsp. You should be able to eliminate javac calls by pre-compiling your jsp pages.
Now, as I have not yet started using tc v.5.x I am not sure if this will help, but in 4.1.x there is a switch in /tomcat/conf/web.xml to set the jsp compiler engine to forc the process. I recomend that you check that one out.
In my opinion, if you are using tomcat in production environment you should turn of any "reloading-options" as they will always collect memory. that means context reloading, auto-deployment, jsp reloading and developement switches.
By doing that you will minimize the overhead (both process and memory) of tomcat, leaving only the basic footprint of tomcat with the current configuration.
Hope it helps -reynir
java only wrote:
Hi All,
I have seen in Tomcat 5.0.25 Release notes the JAVAC Leaking memory problem is mentioned. Earlier I was using Tomcat 3.3.1 and was getting java.lang.OutOfMemory Exceptions after every 2-3 days and had to restart my Tomcat Server.I am planning to migrate to Tomcat 5.0.25 version , but here too seems is the same problem .I am using jdk 1.3.1 version. If I use jdk 1.4 version,would this problem be resolved? Or is there any way to get around this problem ..?
Any feedback is welcome...
Thanks in Advance,
javaonlyjava.
--------------------------------- Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
