Of course, it exposes customers to the security holes Oracle supposedly patched in 7u71 and 8u25, but our product is generally used behind a firewall.

That release works with or without the parentClassLoader property. Right now the only 'fix' for the problem I can give my customers is to have them uninstall any Java 7 or Java 8 JREs and (re)install Java 7 update 67. The attempt to instantiate the class comes from. (StreamHandlerFactory.java:102). With the property set, there are no errors in the web start trace, but now there's a ClassCircularityError on /org/eclipse/osgi/framework/util/SecureAction$19 in the eclipse log. Without it I saw an AccessControlException in the web start trace, caused by EclipseLog.checkLogFileSize. It did cause a change in the launching process, but it didn't fix it. Unfortunately, setting the (jnlp.)osgi.parentClassLoader property didn't work for me. : .NLSДЄt .(EclipseStarter.java:200)ДЄt 0(Native Method)ДЄt (Unknown Source)ДЄt (Unknown Source)ДЄt .invoke(Unknown Source)ДЄt .Main.invokeFramework(Main.java:620)ДЄt .Main.basicRun(Main.java:575)ДЄt .WebStartMain.basicRun(WebStartMain.java:79)ДЄt .n(Main.java:1408)ДЄt .WebStartMain.main(WebStartMain.java:57)ДЄt .executeApplication(Unknown Source)ДЄt .executeMainClass(Unknown Source)ДЄt .doLaunchApp(Unknown Source)ДЄt .run(Unknown Source) !MESSAGE Exception launching the Eclipse Platform: Not getting any messages about jar signing issues. This breaks my company's web-start RCP application. Oracle just released java 7 update 71 and 72.

Java 7 update 40