Community
Participate
Working Groups
There are some platforms that still default to forking the vm in a separate process because those platform originally had problems with the JNI invocation API which seem to be better with modern vms. We should consider changing to use JNI by default. All the linux platforms except x86 currently default to forking the vm, as well as hpux.
Given bug 339788 can this be configurable? I primarily use x86_64 and it has been useful in the past for me to see the Java invocation command (to debug launch parameters, etc.). Presumably jstack, jps, jconsole etc. work for the JNI'd java?
On all platforms except the mac, you can specify which one to use by setting the -vm argument. If the -vm arg points to a java executable, then we will fork. If the -vm arg points to a (libjvm.so/jvm.dll) shared library, then we will attempt JNI invocation.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This bug was marked as stalebug a while ago. Marking as worksforme. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
