Tomcat doesn't free any memory related to servlets. It creates them
as needed (either at startup if loadonstartup is specified or on first
access) and then holds onto them for as long as it wants. There is no
requirement as to when the servlet goes out of memory since it can use the
same instance for hundreds of requests. If I had to guess, you are hanging
onto memory that you don't need any more, planning on the instance going out
of scope. This is generally bad since a single instance can be used to
handle multiple requests.
The other possible thing that you are seeing is that the JVM doesn't
give its memory back to the OS right away. This varies by JVM, but all of
them hang onto the memory for a while, just in case they will need it again.
Randy
> -----Original Message-----
> From: Hawkins, Keith (Keith) [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, November 29, 2001 1:51 PM
> To: tomcat-user
> Subject: Known Memory clean-up issues?
>
>
>
> Are there any known issues with Tomcat not freeing up memory properly?
>
> My test of a repeated access to a servlet results in an ever
> increasing
> memory size for
> the Tomcat process. This is bad.
>
> Thanks,
> Keith
>
>
>
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
