-
Bug
-
Resolution: Fixed
-
P3
-
6
OS - Windows XP, Linux JDS, Redhat EL4.0
Steps to reproduce :
Launch the following 2 applications one by one :
http://web-east.east/www/tests/1.6.0/6343114-2/hello1.jnlp
http://web-east.east/www/tests/1.6.0/6343114-2/hello2.jnlp
Now check if there are any javaw processes running
On Linux : $ps -ef | grep javaw
On Windows, Open the windows task manager and check if there are any javaw processes running
Expected behavior - No javaw processes should be running
Actual behavior - javaw process are still running
Note - This problem is not seen on Solaris. On Solaris, after launching the two apps above, ps -ef | grep javaw shows no javaw process running.
Steps to reproduce :
Launch the following 2 applications one by one :
http://web-east.east/www/tests/1.6.0/6343114-2/hello1.jnlp
http://web-east.east/www/tests/1.6.0/6343114-2/hello2.jnlp
Now check if there are any javaw processes running
On Linux : $ps -ef | grep javaw
On Windows, Open the windows task manager and check if there are any javaw processes running
Expected behavior - No javaw processes should be running
Actual behavior - javaw process are still running
Note - This problem is not seen on Solaris. On Solaris, after launching the two apps above, ps -ef | grep javaw shows no javaw process running.
- relates to
-
JDK-6343114 javaw process keeps alive after the jnlp app's "main-class" ending
-
- Resolved
-