Re: Tomcat 4.1.12 memory leak, resources leak, what to do ?

["Ing. Damiano Bolla" <da...@infotechsrl.it>]

Thanks to all that have replied, the problem is still here and what follows 
are the tests I did
To clear the issue here it is what I am doing

----------
- Clean install of redhat 7.2 or Suse 7.1 (same results for both platforms)
- Clean installation of tomcat 4.1.12
- Clean installation if JDK 1.4.1 (the same happens with 1.4.0.2 or 1.3.1)
- What I am doing is http://localhost:8080/  and keep refreshing that with F5
- I am NOT testing my own servlet. I am NOT doing anything else !!!

I monitor memory usage using top and sorting the results by memory. I am 
looking at the SIZE column.
What I get is an EVER INCREASING memory usage. Something like
30212
30220
31016
31040
31576

-------------
I did try the various suggestions and as far as I can tell it is not a 
pure  memory issue but it probably is a resource issue, maybe a file not 
closed or a socket .......
The question, what should I do next ?
Who should I report the problem to ?

I must say that it is very easy to reproduce.....

Damiano



At 20.11 26/09/2002 -0500, you wrote:
>The easiest way to track JVM garbage collection is to start java with the
>"-verbose:gc" arg.  This enables GC data output to stdout.
>
>Regards,
>
>Glenn
>
>
>Raj Saini wrote:
>>I am experiencing the same problem with tomcat 4.0.3. I have my JVM memory
>>setting as -Xms=32 -Xmx=384 and running the tomcat on Sun Solaris 2.7,
>>integrated with Apache 1.3.x through warp connector.
>>I have a JSP page monitoring the memory consumption at
>>http://www.emerging-trade.pt/servlets/memory.jsp, The memory consumption
>>pattern of the JSP shows the GC runs as you can see the increase/decerece in
>>the free memory of the current heap size.
>>Raj Saini
>>Raj Saini
>>----- Original Message -----
>>From: "Tim Funk" <fu...@joedog.org>
>>To: "Tomcat Users List" <to...@jakarta.apache.org>
>>Sent: Thursday, September 26, 2002 2:29 PM
>>Subject: Re: Tomcat 4.1.12 memory leak
>>
>>
>>>Each request allocates memory. (And relinquishes accordingly) The
>>>garbage collector runs when "it feels like it should". The JVM will
>>>continually suck up memory until it reaches its startup parameters. (-mx
>>>...)
>>>
>>>Once a JVM takes memory from the OS - it does not release it to the OS -
>>>it only releases it to its own memory heap.
>>>
>>>Ing. Damiano Bolla wrote:
>>>
>>>>System: Linux redhat 7.2
>>>>Java: /usr/local/j2sdk1.3.1
>>>>Tomcat 4.1.12
>>>>
>>>>To reproduce the behaviour you install the 4.1.12 distribution, set the
>>>>JAVA_HOME run startup.sh and then keep refreshing the homepage
>>>>http://localhost:8080/
>>>>
>>>>If you monitor the memory usage using top and switching it into display
>>>>memory usage (Capital M) you sull see tipically something like
>>>>
>>>>22824
>>>>22832
>>>>22840
>>>>23576
>>>>23676
>>>>23684
>>>>23904
>>>>23908
>>>>23934
>>>>23938
>>>>.....
>>>>
>>>>This is the SIZE field of the top command.
>>>>The point is that it never goes down and eventually you run very slowly.
>>>>
>>>>Any idea ?
>>>>
>>>>Ah, the same behaviour is with jdk 1.4.1
>>>>
>>>>Damiano
>>>>
>>>>
>>>>--
>>>>To unsubscribe, e-mail:
>>>><ma...@jakarta.apache.org>
>>>>For additional commands, e-mail:
>>>><ma...@jakarta.apache.org>
>>>>
>>>>
>>>
>>>--
>>>To unsubscribe, e-mail:
>><ma...@jakarta.apache.org>
>>
>>>For additional commands, e-mail:
>><ma...@jakarta.apache.org>
>>
>>--
>>To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
>>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>
>
>--
>To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>