I update my jsvc lauch script with -Xms and -Xmx options, but I have the same
situation: once the memory has been taken is never released, free memory is
constantly lowering at a lower rate than before, buf lowering.
$DAEMON_HOME/bin/jsvc \
-user $TOMCAT_USER \
-home $JAVA_HOME \
java has brought the best results to us.
bye Philipp
Marco Rossi <[EMAIL PROTECTED]>
01/16/2006 12:17 PM
Please respond to
"Tomcat Users List"
To
Tomcat Users List
cc
Subject
Re: Jsvc memory management experiences
For performance reasons, Tomcat tends to hold on
For performance reasons, Tomcat tends to hold onto the memory that it
allocates, and reuses it.
Interesting enough: but when memory is needed no more, shoud it be collected
out and brought it back to the system as available memory, or is is a normal
situation that memory once obtained is never
"Marco Rossi" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi all,
>
> I've searched in list archive and I've found a discussion about tomcat
> memory occupation [1]. I sucessfully deployed my first production web
> app using jsvc on Fedora Core 4, to allow tomcat on port 80.
> From: Marco Rossi [mailto:[EMAIL PROTECTED]
> Subject: Jsvc memory management experiences
>
> I noticed that memory used is never released back to
> the system after the requests have been satisfied.
This is standard JVM behavior. The JVM rarely shrinks the heap, and if
a
Hi all,
I've searched in list archive and I've found a discussion about tomcat memory
occupation [1]. I sucessfully deployed my first production web app using jsvc
on Fedora Core 4, to allow tomcat on port 80.
Using tomcat 5.5.12 and java 1.4.2_10 ( 1.5 is not usable due to a javamail
compat
