"holtak" wrote : we also had PermGen problems | | Can confirm that JRocket helps with PermGen problems. | | You could try SUN JVM 1.6.0 update1 - it suspiciously works here untill now but maybe the server wasn`t just stressed enough and there seams to be no significant change in the SUN changelog regarding this issue... | | We also tried JRocket and are using it now in development and testing environment. It really solves the PermGen issue because there is no separate Permanent Generation of a garbage collectable memory in JRockit JVM, but it does not solve memory leaks that exist in somewhere in container or application code. Memory still leaks, the allocated heap grows, and after all, OutOfMemory condition still occures, though the system survives many more hot deploy cycles. The ultimate solution to the problem would be an application and an application container that do not leak memory. The problem is there, not in the Java VM, or the memory configuration parameters. The system is leaking - it will crash sooner or later no matter what JVM or how much memory is configured. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062831#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...