tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeffrey Janner" <>
Subject RE: java.lang.OutOfMemoryError: PermGen space
Date Wed, 16 Sep 2009 14:30:39 GMT
Chuck -
I couldn't tell from the post if the Architecture line meant hardware,
OS, or JVM.  And I'm under the impression from multiple re-reads of the
Java tuning docs that ALL generations are drawn from the heap, including
Yes, using Jconsole or better is what he needs to do.

Here is another good read.  Direct from Sun:

-----Original Message-----
From: Caldarale, Charles R [] 
Sent: Wednesday, September 16, 2009 9:04 AM
To: Tomcat Users List
Subject: RE: java.lang.OutOfMemoryError: PermGen space

> From: Jeffrey Janner []
> Subject: RE: java.lang.OutOfMemoryError: PermGen space
> You don't say if the JVM is 32-bit or 64-bit

Actually, he did:

> Architecture:   amd64
> JVM Version:    1.6.0_16-b01
> JVM Vendor:     Sun Microsystems Inc.

The architecture would be x86 for a 32-bit JVM on Intel/AMD.

> 1) By splitting the Heap in half between NewGen and PermGen

This is not correct.  The -Xmx size does not include the PermGen size.

Again, use JConsole or equivalent to verify that the requested heap
sizes are being used.

 - Chuck

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 unsubscribe, e-mail:
For additional commands, e-mail:

*******************************  NOTICE  *********************************
This message is intended for the use of the individual or entity to which 
it is addressed and may contain information that is privileged, 
confidential, and exempt from disclosure under applicable law.  If the 
reader of this message is not the intended recipient or the employee or 
agent responsible for delivering this message to the intended recipient, 
you are hereby notified that any dissemination, distribution, or copying 
of this communication is strictly prohibited.  If you have received this 
communication in error, please notify us immediately by reply or by 
telephone (call us collect at 512-343-9100) and immediately delete this 
message and all its attachments.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message