Name: joT67522			Date: 11/19/97


Bug 4087072 is not my request (although similar).  I am not referring to any 
of the tools of the JDK but to a problem (at least one perceived on my part) 
with the JVM & the JNI Invocation API.

If I am invoking a JVM from a native process I want to be able to end the JVM 
and continue doing other work.  My problem is that when a call to System.exit() 
is made from inside the JVM, the entire native process (not just the JVM threads) 
is killed.  Also, the JNI Invocation API call DestroyJavaVM() does not unload the 
JVM (as it claims it does in the API documentation).  What I would like is for either 
System.exit() not to kill the entire process (maybe just the main thread it was 
invoked from) or for the JNI Invocation API call DestroyJavaVM() to actually unload 
the JVM and reclaim its resources.  Either of these fixes would allow me to continue 
processing.

What I am really looking for is a commitment on when these problems will be 
fixed or addressed (JDK 1.1.5? 1.2? 2.0?).  I have had a couple of people contact 
me about a posting I made in the Java newsgroups about this issue.  They are 
also interested in a timeframe on the resolution of this bug.

======================================================================