tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reynir Þór Hübner <>
Subject Re: JAVAC Leaking Memory
Date Mon, 07 Jun 2004 09:55:15 GMT

java only wrote:

> Does It mean setting the fork option to true in the conf/web.xml file ? I have also set
development and reloadable option to false...

no. It does not mean that. you can set fork option to false, and 
reloadable/developement to true or vice versa, anyway you like. But I 
still recomend that in production environment you set developement to 
false and reloadable to false.

setting fork option to true will throw avay the javac process when it's 
done it's work, leaving no memory leaks, but I think it's a little bit 
slower than fork=false. I'm not sure, maybe someone else can answer that.

> And also I have noticed for each session,for the first time it takes lot of time to load
JSP page and hence forth the loading of those pages is quick. Does it 
mean JSP pages compile
first time and not afterwards for that session?

Page compilation is only done once for each jsp document. I think your 
session lagging has to do with something else, some session related 
code/rendering etc.

hope it helps


> Thanks,
> JavaOnlyJava
> "Shapira, Yoav" <> wrote:
> Hi,
> Good advice. The fork option for jasper exists in tomcat 5, it's key to helping with
these sorts of problems.
> Yoav Shapira
> Millennium Research Informatics
>>-----Original Message-----
>>From: Reynir Þór Hübner []
>>Sent: Friday, June 04, 2004 7:34 AM
>>To: Tomcat Users List
>>Subject: Re: JAVAC Leaking Memory
>>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
>>Hope it helps
>>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,
>>>Do you Yahoo!?
>>>Friends. Fun. Try the all-new Yahoo! Messenger
>>To unsubscribe, e-mail:
>>For additional commands, e-mail:
> 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:
> For additional commands, e-mail:
> ---------------------------------
> Do you Yahoo!?
> Friends.  Fun. Try the all-new Yahoo! Messenger

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message