I've learned that you can use "-Xms128m -Xmx256m" (The "java" command line
option) which means the heap will start at 128m and
grow to 256m
If you haven't done so, It would be best testing your app first (use
verboseGC)
to check the memory usage and then setting both parameters to the same no.
I got the following lines from one of the emails which you may find useful:
...To set this, you can establish an environment variable
named TOMCAT_OPTS (Tomcat 3.x) that contains
the command line options to be sent to the JVM. For example:
export TOMCAT_OPTS="-Xmx256m"
$TOMCAT_HOME/bin/tomcat.sh start
HTH.
:~)
Ricky Y. Artigas
Analyst/Programmer /
Database Administrator
Information Technology Division
Easycall Communications Phils., Inc.
> -------------------------------
> IMPORTANT NOTICE:
> This message (and any attachment hereto) may contain privileged and/or
> confidential information specific to EasyCall. If you are not the intended
> addressee indicated in this message, you may not copy or disseminate this
> message (or any attachment hereto) to anyone. Instead, please destroy this
> message (and any attachment hereto), and kindly notify the sender by reply
> email. Any information in this message (and any attachment thereto) that
> do not relate to the official business of EasyCall shall be understood as
> neither given nor endorsed by the company.
>
>
> -----Original Message-----
> From: Matt Fisher [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, September 27, 2001 9:06 AM
> To: [EMAIL PROTECTED]
> Subject: OutOfMemoryError from Tomcat 3.2
>
> Hello,
>
> I have an application running on a Windows2000 server, using Tomcat 3.2,
> Apache
> 1.3.20, and a SQL Server 2000 database. This application will be going
> live next
> week. The initial user base will be approximately 20, but ultimately we
> will
> have a user base of 100+.
>
> During our stress testing today (approximately 20 simultaneous sessions),
> we
> started getting a lot of errors (java.lang.OutOfMemoryError) on the
> server. The
> errors are logged in Tomcat's jvm.stderr logfile. They started occurring
> during
> the stress test, and stopped occurring thereafter.
>
> I have read that on Solaris, Tomcat 3.2 may get OutOfMemory errors if
> there are
> too many sessions at one time. Our server is running Windows 2000, but I
> wonder
> if our problems also stem from too many sessions. If so, is there a
> parameter we
> can tweak, a fix for Tomcat 3.2, or a new release which addresses this
> issue?
>
> During a previous incident where OutOfMemory errors were occurring, I
> checked
> the Windows 2000 performance monitor. Memory usage was approximately 10%
> of the
> 1 gigabyte capacity. It strikes me as odd that we'd get OutOfMemory
> errors,
> unless the JVM only has access to a small portion of the machine's memory.
>
> We also saw "index out of bounds" errors during the stress test, but I am
> guessing that this is somehow related to the memory errors.
>
> Any help you can provide would be appreciated.
>
> Yours,
>
> - Matt Fisher
> . . . . . . . . . . . . . . .
> Matthew J. Fisher
> Applications Programmer
> University of Chicago Press
> 1427 E. 60th Street
> Chicago, IL 60637-2954
> Tel 773-834-5386
