@jdillon No, Jetty does not provide anything in this area yet.

To repeat, the problem is that there is _no feedback_ (in logs, visible) that OOM happened. This QTP modification was just a "best effort" try to make Nexus (well, Jetty) start nagging you if it detected "thread loss" from pool. Simply, you (the ops running Nexus) can be completely unaware of the fact that there was an OOM in system.

After reading a bit more, am leaning towards Greg stance, I am fine with your change (removing this customized QTP and replacing it with Yammer one), and we should just recommend putting `-XX:+HeapDumpOnOutOfMemoryError` into wrapper.conf... as that's the best you could do so far.