This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Product Version = NetBeans IDE 7.2 (Build 201207130001) Operating System = Windows 7 version 6.1 running on amd64 Java; VM; Vendor = 1.7.0_06-ea Runtime = Java HotSpot(TM) 64-Bit Server VM 23.2-b08 Pre-FX Webstart seems to be used to run FX App jnlp file, when I set following VM Options: -Dhttp.proxyHost=proxy.mydomain.com -Dhttp.proxyPort=80 java -version java version "1.7.0_06-ea" Java(TM) SE Runtime Environment (build 1.7.0_06-ea-b19) Java HotSpot(TM) 64-Bit Server VM (build 23.2-b08, mixed mode) I'm not aware of any unusual system settings and I didn't test any other JDK yet.
Created attachment 122009 [details] AudioVisualizer3D.jnlp Might be related to http://javafx-jira.kenai.com/browse/RT-21705. The automatic proxy setting works fine for me with FX Applications on FX 2.2, so there is no need to set those options, but once they're in a jnlp file, the problem occurs. Attaching jnlp file of FX Application generated by NB 7.2 on JDK7u6. The proxy settings are on line 13. If I just delete them, it starts to run correctly.
I tried to reproduce the problem with current JDK7u21 containing FX 2.2.21. I could not reproduce it. I tried the same AudioVisualizer3D sample, added proxy settings in the same way to VM options in FX Project Properties and the current observed behavior is this: with valid proxy it worked for me, with invalid proxy I could still see that the FX engine has started because the initial FX scene has been created and parts of the demo became visible until the code froze on an attempt to access non-existing proxy. Apparently the current WebStart technology does recognize FX App correctly and does launch it according to FX WebStart model. The root of the problem described in this issue is likely to have disappeared after a series of substantial changes in WebStart technology that took place in early 2013. Closing as unreproducible.