> 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 responsibility for bugs in your own code? > By default (at least, if you're using Sun Java), a Java process > is given 32Mb of "PermGen" memory. If you have the "-server" > flag set for your Java process, the default is 64Mb. No, the default maximum is 64MB for both client and server modes, at least in the 1.5 and 1.6 JVMs. The initial size is different for client and server, but that's largely immaterial. > To set the upper-bound of PermGen space, then, use the flag: > "-XX:MaxPermSize=#m". This is most likely all that's needed, since there does not appear to be any redeployment involved. There are simply too many classes defined for the default PermGen size. Here's a good starting point for descriptions of GC and heap operations: http://java.sun.com/javase/technologies/hotspot/gc/index.jsp Setting -Dcom.sun.management.jmxremote and running JConsole with Tomcat can provide useful information about what's going on with JVM memory. - 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]
