> From: Jim [mailto:[EMAIL PROTECTED]
> Subject: Re: PermGen Out of memory exception
>
> The problem with that language is it implies that PermGen space is
> generally only an issue if you're using a lot of servlets or JSPs.
Agreed, that's not inclusive enough.
>
Caldarale, Charles R wrote:
Perhaps the Tomcat FAQ on memory-issues could be fleshed
out/updated?
This specific item is already in the Tomcat FAQ:
"If you have a lot of servlets or JSP's, you may need to increase your
permanent generation. By default, it is 64MB. Doubling [sic] it to be
> From: Jim [mailto:[EMAIL PROTECTED]
> Subject: Re: PermGen Out of memory exception
>
> To address your rhetorical question :) , this issue is a
> mess to research.
Which is why it should be done before deployment...
> it can be intimidating to be pointed at a 21 page
>
Caldarale, Charles R wrote:
From: Jim [mailto:[EMAIL PROTECTED]
Subject: Re: PermGen Out of memory exception
PermGen space, on the other hand, doesn't get garbage collected
As Peter C indicated, this is utter BS. Why do people keep propagating
this fallacy? Easier to blame th
> From: Jim [mailto:[EMAIL PROTECTED]
> Subject: Re: PermGen Out of memory exception
>
> PermGen space, on the other hand, doesn't get garbage collected
As Peter C indicated, this is utter BS. Why do people keep propagating
this fallacy? Easier to blame the JVM than take r
> From: Jim [mailto:[EMAIL PROTECTED]
> PermGen space, on the other hand, doesn't get garbage
> collected, so you
> need to ensure you're allocating enough to handle all that your
> application will need. Unfortunately with the web application
> classloader-system, every time you deploy an applica
Hi Kanchana,
Java processes use two types of memory: the "heap" (which is garbage
collected), and "PermGen" memory (which is not garbage collected).
Generally speaking, you won't run out of heap memory unless your
application is set up so that the memory for all the objects being used
at a s
