FULL PRODUCT VERSION :
java version "1.3.0_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0_02)
Java HotSpot(TM) Client VM (build 1.3.0_02, mixed mode)

FULL OPERATING SYSTEM VERSION :
Win NT4

A DESCRIPTION OF THE PROBLEM :
JWS litters $WINUSERHOME\Local Settings\Temp and d:\TMP
where $WINUSERHOME is d:\winnt\profiles\$MYLOGIN

Some files are called javawsN
where N is a number

All files are temporary files.
If not removed, I observe odd behaviour of all sorts, like
instability or failure of installing a JRE.

The worst thing I observed:
I have a class that loads native classes via System.loadLibrary() for JMF 
video playback.  I commented out that call, and added some println("I'm here") 
to be sure.  I was getting "I'm here" (thus not loading native libs), but could
still watch video.  I installed a fresh JVM to make sure that I was not using 
the native libs from the JVM.  I scanned all my drives for the native libs 
(only present in the JNLP-cache).  
I rebooted.
I concluded, that the JVM was using the native libs in the JNLP-cache without
loadLibrary().
I removed the tmp-files.
I was not longer able to watch video, and I had to uncomment loadLibrary().

I am not able to reproduce but I have a strong feeling that the tmp-files 
are the reason for my observation.

Temporary files should not be written.


This bug can be reproduced occasionally.
(Review ID: 143800) 
======================================================================

N/A

we create a copy of the applications jnlp file in the native code.  we should remove the copy if we do not need it anymore.

however I cannot relate this to customer's comment on native lib loading.

changing it to a bug instead of eou.


 xxxxx@xxxxx  2002-04-08

One way to reproduce the problem:

1.  set proxy to null (so it cannot get to the internet)
2.  launch one of the demos from java.sun.com using the browser.
3.  you will see a launch error.
4.  temp file gets left behind.


 xxxxx@xxxxx  2002-04-17