Gabe, Quite like that. In my case, we didn't exceed the amout of physical memory available, but as our server shared its resources with other applications, it happened lots of times...
-----Mensagem original----- De: Gabe Wong [mailto:[EMAIL PROTECTED] Enviada em: segunda-feira, 17 de março de 2008 11:41 Para: Tomcat Users List Assunto: Re: RES: about java.lang.outofmemory error Milanez, Marcus wrote: > Chuck, > > Sorry if I haven't been clear enough, but we did have several situations in > which such a thing happened in production. We'd specified too much memory to > tomcat, and as our server shared its physical with other applications such as > IIS, GC never (ever) ran and Tomcat proccess could never acquire the amout of > memory we'd specified, causing java.lang.OutOfMemory error plenty of times. > We could just solve it decreasing tomcat's proccess initial and maximum > amount of memory, that's why I've warned about it. I really apologize if I'm > wrong, but is there another explanation for it? > > It sounds like in your case, you were allocating more memory to the JVM that was available from the system. Thus quite naturally when you lowered the allocation you encountered less problems. However if your application had indeed required the larger allocation, you would have experienced OutOfMemory. Point is, larger memory allocation is a good thing, but it cannot exceed what is available on the system. -- Regards Gabe Wong NGASI AppServer Manager JAVA AUTOMATION and SaaS Enablement http://www.ngasi.com NEW! 8.0 - Centrally manage multiple physical servers --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
