> From: Rashmi Rubdi [mailto:[EMAIL PROTECTED] > Subject: Re: tomcat 5.5 > > So, having a lower heap size limit (lower max memory > setting), ensures that the garbage collector releases as much > memory as possible in a shorter interval and having a higher > memory setting significantly delays the garbage collection.
Actually, the length of time spent in GC is almost entirely dependent on the number of live objects and not the size of the heap. The number of live objects fluctuates a relatively small amount for most applications, so it's usually beneficial to run with as large a heap as you can get away with. In this case, the JVM isn't running out of heap space - it's the underlying OS that's refusing to create additional threads when the JVM heap is enlarged enough to impact the remaining virtual space for the process. Might be something as simple as not having a large enough swap file. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
