No, there is no timeout. When an object needs to be allocated and there is no room, the app is stopped until the garbage collector is done, and then allocation happens. Unless you are running the concurrent collector. I have never seen such a huge drop in the perm gen. The output you showed looks to be from -XX:+PrintGCDetails, not -XX:+PrintHeapAtGC. The later also prints a list of classes freed, it would be interesting to see what classes were garbage collector during that last collection. What is the full stack trace for the OutOfMemory exception? Perhaps knowing what was being allocated might help debug this issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073701#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...