This content has been marked as final. 
    
Show                 2 replies
    
- 
        1. Re: JVM Crashstarksm64 Feb 4, 2005 5:36 PM (in response to david.salter)-Xmx has no affect on the permanent generation heap size. See: 
 http://java.sun.com/docs/hotspot/VMOptions.html
- 
        2. Re: JVM Crashdavid.salter Feb 25, 2005 7:22 AM (in response to david.salter)Do you mean: -XX:MaxPermSize=64m 
 I've set this higher and it makes no difference. Relevant parts of the error trace are below:Heap def new generation total 26240K, used 23310K [0x02a20000, 0x04690000, 0x04690000) eden space 23360K, 99% used [0x02a20000, 0x040e2a20, 0x040f0000) from space 2880K, 0% used [0x040f0000, 0x040f1150, 0x043c0000) to space 2880K, 0% used [0x043c0000, 0x043c0000, 0x04690000) tenured generation total 233024K, used 46801K [0x04690000, 0x12a20000, 0x12a20000) the space 233024K, 20% used [0x04690000, 0x07444468, 0x07444600, 0x12a20000) compacting perm gen total 34048K, used 33959K [0x12a20000, 0x14b60000, 0x1aa20000) the space 34048K, 99% used [0x12a20000, 0x14b49d28, 0x14b49e00, 0x14b60000) No shared spaces configured. VM Arguments: jvm_args: -Dprogram.name=run.bat -Xms256m -Xmx256m -XX:MaxPermSize=128m -Djava.endorsed.dirs=C:\Devtools\java\jboss-4.0.1\bin\\..\lib\endorsed java_command: org.jboss.Main -c all 
 
    