ut java.lang.outofmemory error
From: Milanez, Marcus [mailto:[EMAIL PROTECTED]
Subject: RES: about java.lang.outofmemory error
GC never (ever) ran and Tomcat proccess could never acquire the amout
of memory we'd specified
The fact that GC never ran is irrelevant. As someone else poin
PROTECTED]
Enviada em: segunda-feira, 17 de março de 2008 12:16
Para: Tomcat Users List
Assunto: RE: about java.lang.outofmemory error
> From: Milanez, Marcus [mailto:[EMAIL PROTECTED]
> Subject: RES: about java.lang.outofmemory error
>
> GC never (ever) ran and Tomcat proccess c
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 mu
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
is there another explanation for it?
Thank you!
-Mensagem original-
De: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Enviada em: segunda-feira, 17 de março de 2008 11:06
Para: Tomcat Users List
Assunto: RE: about java.lang.outofmemory error
> From: Milanez, Marcus [mailto:[
Hello,
Just be aware that increasing memory isn't always the best option. In most
cases you should decrease memory instead, giving GC a chance to run. If you
increase memory, it may never run (realising unused resources) and your process
may never be able to allocate the amount you specify...
