The error thrown when memory is exhausted is constructed at jvm boot time, otherwise it might not have enough memory to even construct that Throwable object on the heap.
So there is no way to intercept the new OutOfMemoryError() when it is actually thrown, because it is not constructed at that time. Assuming that memory is already exhausted (and it is some other problem like thread construction), you wouldn't be able to do anything anyway. Trying to handle any of the JVM internal errors is a crapshoot. The JVM itself has already given up and failed the request. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3874670#3874670 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3874670 ------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
