When a weblogic server is hit by an OutOfMemory condition, it often agonizes for a while before finally collapsing. This is not very healthy for the poor beast, and for humanitarian reasons you might want to end its suffering sooner.
OnOutOfMemoryError is a little-know flag documented here http://www.oracle.com/technetwork/articles/java/vmoptions-jsp-140102.html
Try starting the JVM with -XX:OnOutOfMemoryError="kill -9 %p" or -XX:OnOutOfMemoryError='kill -9 %p' and see if this does the job. I haven't tested this flag yet.
OnOutOfMemoryError is a little-know flag documented here http://www.oracle.com/technetwork/articles/java/vmoptions-jsp-140102.html
Try starting the JVM with -XX:OnOutOfMemoryError="kill -9 %p" or -XX:OnOutOfMemoryError='kill -9 %p' and see if this does the job. I haven't tested this flag yet.