RFR(xs): 8213834: JVMTI ResourceExhausted should not be posted in CompilerThread

[Glyn Normington]

Another solution which I don't think has been considered in this thread
would be to give the resource exhaustion exit some way of determining
whether it is being driven on a compiler thread in which case the exit
could skip the analyses which run into the JVM internal error.

I couldn't find a way to do this as the relevant header files are internal
to Hotspot and not exposed on JVMTI or JNI.

As was mentioned earlier, there is more context in:
https://github.com/cloudfoundry/java-buildpack/issues/500 (which was closed
because we couldn't find a solution, in spite of a solution being very
desirable).

Regards,
Glyn