tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <>
Subject RE: Tomcat 4.0.x memory leak (not javac)
Date Mon, 01 Dec 2003 20:23:13 GMT

First, prove to us it's the same "bug."  I say "bug" in quotes when referring to the original
issue because I have no clue what's being discussed unless someone posts a bugzilla ID for

Yoav Shapira
Millennium ChemInformatics

>-----Original Message-----
>From: Abhijeet Selukar []
>Sent: Tuesday, November 11, 2003 2:49 AM
>To: Tomcat Users List
>Subject: Re: Tomcat 4.0.x memory leak (not javac)
>I am also facing the same problem of memory leakage. I have posted on mail
>about this on 19th Nov too...
>I had contacted to the support people where our web application is hosted.
>I had got few suggestions. According to their suggestion -
>1. I increased the heapsize in file.
>2. I have also tried to increase the file descriptor size.
>Increaing the file descriptor size helped me at some extent. It stopped the
>frequent exceptions in Tomcat -> catalina but occasionaly I am still gettng
>same exceptions.
>I would really like to have some more suggestions.
>Abhijeet Selukar
>  ----- Original Message -----
>  From: Trenton D. Adams
>  To: Tomcat Users List
>  Sent: Monday, December 01, 2003 12:21 AM
>  Subject: Re: Tomcat 4.0.x memory leak (not javac)
>  Sven Köhler wrote:
>  >>>>> It's a known bug, but not fixed in 4.1.x, it still exists there.
>  >>>>> am not sure if it still exists in 5.0.x.
>  >>>>
>  >>>>
>  >>>> Thanks Dave.  If anyone could provide some more information on this,
>  >>>> that would be helpful.  I would really like to fix it because it's
>  >>>> really annoying me.  We have two CRITICAL web applications on one
>  >>>> server.  We don't want to have to continually down the entire tomcat
>  >>>> server just to reload a webapp.
>  >>>
>  >>>
>  >>> Bugs have been filed for this issue against 4.1.x and they have been
>  >>> marked as WONTFIX.  Best to try to reproduce the problem on 5.0.x and
>  >>> if the bug still exists there, file a report in bugzilla if one does
>  >>> not already exist.
>  >>
>  >>
>  >> Where can I find this information?  Is there a bugzilla for tomcat or
>  >> something?  If so, I would like to go there so I can see if there's
>  >> any information indicating where in the code it would be.  I could go
>  >> searching myself, but I've never dove into the Tomcat code before! :)
>  >
>  >
>  > Could you post the bugid or even a link to the bug-report? i'm also
>  > interested in the porblem.
>  >
>  > I would also be interested in a description of the javac-memory-leak.
>  > has become a "myth" and nobody can explain it. I don't find a bug-
>  > in both Sun's and Tomact's bug-databases.
>  I found it once but I can't find it again.  I was pretty sure I entered
>  "memory leak" in the summary field and came up with results, but it
>  doesn't work now.
>  Anyhow, the javac bug is referenced in the release notes of 4.0.x.  I
>  don't think it's a javac bug but a tomcat bug with the interface into
>  the javac classes.  After all, it's not referenced in the release notes
>  for the newer versions of tomcat.
>  >
>  >
>  >
>  > ---------------------------------------------------------------------
>  > To unsubscribe, e-mail:
>  > For additional commands, e-mail:
>  >
>  __
>      This communication is intended for the use of the recipient to whom
>      is addressed, and may contain confidential, personal, and or
>      information. Please contact us immediately if you are not the
>      recipient of this communication, and do not copy, distribute, or take
>      action relying on it. Any communications received in error, or
>      subsequent reply, should be deleted or destroyed.
>  ---
>  ---------------------------------------------------------------------
>  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:

View raw message