Hi Karl, >From my understanding (I'd welcome any corrections):
-Xms is the initial size of the JVM heap (the pool of memory available for allocation as variables/objects) -Xmx is a hard limit on the maximum size of the JVM heap. When an object needs to be created the JVM requests memory from its heap. If the current heap usage is near to the current limit then garbage collection may be attempted to free memory. If this doesn't free enough then the heap limit will grow towards the Xmx value. Once the heap size is at the Xmx value and an allocation request occurs, garbage collection will be attempted and if this fails to free enough memory to satisy the allocation then the JVM will throw an OutOfMemory runtime exception. AFAIK the JVM will not allow the heap to grow past the Xmx value (this is a good thing IMHO as it will stop the JVM from taking over the whole machine). I've had problems myself with running out of memory on a 2GByte machine and my solution was to optimize my own code to free resources as soon as possible and to explicity run finalize() and gc(). Hope this helps and I'd be interested if you find any tips on optimizing server-side JVM memory usage. Best Regards, Chris On Friday 30 November 2001 12:57, you wrote: > hi, i am running into problems with my tomcat-3.2.3 installation; > > i have set my TOMCAT_OPTS to "-Xms64M -Xmx512M" but i am still running out > of memory on my server with 2gb with memory. > > when tomcat is spawning new threads it is restricted to the -Xmx value? or > can it eat more memory than stated from the TOMCAT_OPS? > > mvh karl oie > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
