What we are doing is running Tomcat as a service on a production server; we
specify both -Xmx and -Xms values. What we are seeing is that after several
days of use, Tomcat is well over the max, by a magnitude of 100+ MB. Our
experience has been that when we run it manually it seems to stay within the
bounds, but when running as a service it seems to go beyond them. So perhaps
we're not installing the service correctly...

Christian
----------------------------------------------
Christian Cryder [[EMAIL PROTECTED]]
Internet Architect, ATMReports.com
Barracuda - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today"

> -----Original Message-----
> From: Hari Venkatesan [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 28, 2003 10:02 AM
> To: Tomcat Users List
> Subject: RE: Tomcat 4.1 ignoring -Xmx params
>
>
> How did you find out it is ignoring -Xmx parameter. Initially when you
> start up tomcat, it would allocate only the minimum heap that you set in
> -Xms.
>
> Hari
>
>
>
> >-----Original Message-----
> >From: Christian Cryder [mailto:[EMAIL PROTECTED]]
> >Sent: Tuesday, January 28, 2003 11:49 AM
> >To: Tomcat-User
> >Subject: Tomcat 4.1 ignoring -Xmx params
> >
> >Hey folks, has anyone observed scenarios where Tomcat appears to ignore
> >the -Xmx param? We are running 4.1 as a service on Win 2000 Pro, and
> have
> >manually uninstalled/reinstalled the tomcat service as follows:
> >
> >to uninstall:
> >-------------
> >tomcat.exe -uninstall "Apache Tomcat 4.1"
> >
> >to install:
> >-------------
> >tomcat -install "Apache Tomcat 4.1"
> >"E:\sun\j2sdk1.4.1_01\jre\bin\client\jvm.dll" -Xmx256m -Xms128m -
> >Djava.class
> >.path="D:\Program Files\Apache Group\Tomcat
> >4.1\bin\bootstrap.jar" -Dcatalina.home="D:\Program Files\Apache
> >Group\Tomcat
> >4.1" -Djava.endorsed.dirs="D:\Program Files\Apache Group\Tomcat
> >4.1\common\endorsed" -start
> >org.apache.catalina.startup.BootstrapService -params start -stop
> >org.apache.catalina.startup.BootstrapService -params stop -out
> "D:\Program
> >Files\Apache Group\Tomcat 4.1\logs\stdout.log" -err "D:\Program
> >Files\Apache
> >Group\Tomcat 4.1\logs\stderr.log"
> >
> >What we are seeing here is that everything seems to work just fine, but
> >Tomcat does not seem to stop at the 256m max that we are requesting? Is
> >this
> >to be expected? Or are we doing something stupid?
> >
> >Thanks much,
> >Christian
> >----------------------------------------------
> >Christian Cryder [[EMAIL PROTECTED]]
> >Internet Architect, ATMReports.com
> >Barracuda - http://barracudamvc.org
> >----------------------------------------------
> >"Coffee? I could quit anytime, just not today"
> >
> >
> >--
> >To unsubscribe, e-mail:   <mailto:tomcat-user-
> >[EMAIL PROTECTED]>
> >For additional commands, e-mail: <mailto:tomcat-user-
> >[EMAIL PROTECTED]>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to