Well it's definitely not a memory issue then 
sounds like a decent machine.
I'm not sure what the problem is without giving it a try - we'll test it out on the "all" configuration and see what happens here.
Thanks for finding this,
Kevin
sounds like a decent machine.I'm not sure what the problem is without giving it a try - we'll test it out on the "all" configuration and see what happens here.
Thanks for finding this,
Kevin
Hello,
The settings you have are for heap size, and do not affect the Permanent Generation size - which is where you are getting your OutOfMemory errors.
The permanent generation is special because it holds meta-data describing user classes (classes that are not part of the Java language). Examples of such meta-data are objects describing classes and methods and they are stored in the Permanent Generation.
Applications with large code-base can quickly fill up this segment of the heap which will cause java.lang.OutOfMemoryError: PermGen no matter how high your -Xmx and how much memory you have on the machine.
To set a new initial size on Sun JVM use the -XX
ermSize=64m option when starting the virtual machine.
To set the maximum permanent generation size use -XX:MaxPermSize=128m option.
If you set the initial size and maximum size to equal values you may be able to avoid some full garbage collections that may occur if/when the permanent generation needs to be resized.
The default values differ from among different versions but for Sun JVMs upper limit is typically 64MB. And if you are running the 'All' Jboss configuration the default sounds like it is not enough.
Hope this helps,
Steve
The settings you have are for heap size, and do not affect the Permanent Generation size - which is where you are getting your OutOfMemory errors.
The permanent generation is special because it holds meta-data describing user classes (classes that are not part of the Java language). Examples of such meta-data are objects describing classes and methods and they are stored in the Permanent Generation.
Applications with large code-base can quickly fill up this segment of the heap which will cause java.lang.OutOfMemoryError: PermGen no matter how high your -Xmx and how much memory you have on the machine.
To set a new initial size on Sun JVM use the -XX
ermSize=64m option when starting the virtual machine. To set the maximum permanent generation size use -XX:MaxPermSize=128m option.
If you set the initial size and maximum size to equal values you may be able to avoid some full garbage collections that may occur if/when the permanent generation needs to be resized.
The default values differ from among different versions but for Sun JVMs upper limit is typically 64MB. And if you are running the 'All' Jboss configuration the default sounds like it is not enough.
Hope this helps,
Steve
