This option was added in case a customer had a problem with the new thread for low memory events, gc notification events and JMX notifications, since the notification thread must be a Java thread that's visible to observers. Without this option (default true) notifications are made from the ServiceThread, which should not be visible to observers since most of this work is runtime work. Except JVMTI TagMap object free events should be checked - maybe they should be done from a visible java thread?

We should deprecate UseNotificationThread option and always use notification thread. Needs a CSR.