Is there any way to influence an OOME?
I've seen circumstances under which we arrive at a low memory situation (1.4, 1.5) and the garbage collector works exceptionally hard to prevent an OOME but unfortunately the application time to GC time ratio is less very low resulting in poor user experience which means I'd just as soon it died/restarted rather then hobble.
The above scenario lasts for a relatively long time - load based and I believe it was more network load related. ie. near memory threshold, receive remote requests and end up performing GC but fail and get concurrent mode failure (CMS) memory collected but during the collection we end up with more incoming requests which were enqueued by the OS and so immediately after the collection there is a large memory request.