-
Bug
-
Resolution: Fixed
-
P3
-
fx2.0
Running JavaFX uninstaller i ocassionally get prompts to close Netbeans, etc.
I guess this is because they are using java but they are not using JavaFX Runtime!
The real reason is often java webstart process hanging around. Like
igor 4012 3756 0 08:54:54 con 4:51 "C:\Program Files\Java\jre7\bin\jav
aw.exe" -Djnlp.fx.perf=true "-Xbootclasspath/a:C:\\Program Files\\Oracle\\JavaFX
Runtime 2.0\\lib\javaws.jar;C:\\Program Files\\Oracle\\JavaFX Runtime 2.0\\lib\
deploy.jar;C:\\Program Files\\Oracle\\JavaFX Runtime 2.0\\lib\plugin.jar;C:\Prog
ram Files\Oracle\JavaFX Runtime 2.0\lib\jfxrt.jar" -Djnlp.fx=2.0.0 -classpath "C
:\\Program Files\\Oracle\\JavaFX Runtime 2.0\\lib\deploy.jar" -Djnlpx.vmargs=-Dj
nlp.fx.perf=true "-Djnlpx.jvm=C:\Program Files\Java\jre7\bin\javaw.exe" -Djn
Note that it is not even listed in the dialog offering to close apps!
Killing this process makes retry to work.
Detection code needs to be improved to reduce false positives (can we check whether app is using dlls from JavaFX runtime folder?
or lib where conflict was detected) and be able to find real root causes.
This is rather annoying issue in the dev environment and for beta users.
I guess this is because they are using java but they are not using JavaFX Runtime!
The real reason is often java webstart process hanging around. Like
igor 4012 3756 0 08:54:54 con 4:51 "C:\Program Files\Java\jre7\bin\jav
aw.exe" -Djnlp.fx.perf=true "-Xbootclasspath/a:C:\\Program Files\\Oracle\\JavaFX
Runtime 2.0\\lib\javaws.jar;C:\\Program Files\\Oracle\\JavaFX Runtime 2.0\\lib\
deploy.jar;C:\\Program Files\\Oracle\\JavaFX Runtime 2.0\\lib\plugin.jar;C:\Prog
ram Files\Oracle\JavaFX Runtime 2.0\lib\jfxrt.jar" -Djnlp.fx=2.0.0 -classpath "C
:\\Program Files\\Oracle\\JavaFX Runtime 2.0\\lib\deploy.jar" -Djnlpx.vmargs=-Dj
nlp.fx.perf=true "-Djnlpx.jvm=C:\Program Files\Java\jre7\bin\javaw.exe" -Djn
Note that it is not even listed in the dialog offering to close apps!
Killing this process makes retry to work.
Detection code needs to be improved to reduce false positives (can we check whether app is using dlls from JavaFX runtime folder?
or lib where conflict was detected) and be able to find real root causes.
This is rather annoying issue in the dev environment and for beta users.