tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oscar Carrillo <>
Subject RE: Need some Tomcat Configuration help badly
Date Wed, 17 Dec 2003 19:23:58 GMT

If I understand this correctly, there are references lying around that
point to objects that no longer are needed. Is this something the
developer does or something tomcat does in compiling the servlets?

In other words, is there something the developer or administrator can do 
to avoid this? Does pre-compiling the jsp files avoid this?

Another thing I'm not sure I understand is this:

If you don't change the JSP pages, or class files, then the memory leak
that is created just happens once. In this scenario, the memory 
leak wouldn't keep growing until eventually tomcat does. Is that correct?


On Wed, 17 Dec 2003, Shapira, Yoav wrote:

> Howdy,
> Actually, the popularity and usage of Jikes has been decreasing (at
> least as measured by downloads).  Javac's memory-handling behavior has
> been improved significantly.
> The memory leaks described earlier in this thread are not
> compiler-related and simply swapping compilers would not help.  They are
> problems of reference scope.
> Yoav Shapira
> Millennium ChemInformatics
> >-----Original Message-----
> >From: Nikola Milutinovic []
> >Sent: Monday, December 15, 2003 1:16 AM
> >To: Tomcat Users List
> >Subject: Re: Need some Tomcat Configuration help badly
> >
> >Dick Steflik wrote:
> >
> >> I had the same question. In all of the years I've worked with Java
> I've
> >> always thought  it was free of memory leaks. If you use a different
> >> compiler does the problem go away. Is that how people like JRun
> >> (Macromedia)  and WebSphere (IBM) avoid the problem?
> >
> >It could be. Someone here mentioned using Jikes for Tomcat as a
> workaround
> >(solution). I know that Jikes has bugs, here and there, but it can be
> made
> >to
> >work and it comes with Tomcat. Considering that "javac" has an all
> present
> >bug
> >(this memory leak), Jikes is better. I guess commercial solutions use
> their
> >own
> >implementations or fork off to get rid of memory leak.
> >
> >Why does JavaC have that memory leak?
> >
> >Nix.
> >
> >
> >---------------------------------------------------------------------
> >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:

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

View raw message