Can not start the designer using Oracle 7 Java

Hi All

We are running a trial and I’m trying to start the designer using Oracle Java 7. The splash screen displays but then nothing happens. It works perfectly using OpenJDK 7.

I have tried Oracle 7 (1.7.0_21) on both Fedora 16 and Ubuntu 12.10 with no luck, both behave the same. We are running Ignition 7.6.0.

I also tried running the OpenJDK Java web start from the command line, but it still tries to use Oracle Java 7. It doesn’t seem possible to tell the Java web start to use a non default JRE? I can’t change the default Java since it is required for other critical applications to run.

Has anybody else experienced the same problem with Oracle Java 7 or know of a workaround to get it started from the command line or using Oracle Java 7?

Thanks,
Pieter

I found the workaround as mentioned in http://www.inductiveautomation.com/forum/viewtopic.php?f=64&t=9949.

Is there a more permanent workaround? In a live CD/dumb terminal environment you wouldn’t want users to go through a save/copy/edit/run (and don’t use the shortcut) process every time they reboot. Is there a known source/settings fix that will serve the file without the additional parameters?

[quote=“pvanderm”]I found the workaround as mentioned in http://www.inductiveautomation.com/forum/viewtopic.php?f=64&t=9949.

Is there a more permanent workaround? In a live CD/dumb terminal environment you wouldn’t want users to go through a save/copy/edit/run (and don’t use the shortcut) process every time they reboot. Is there a known source/settings fix that will serve the file without the additional parameters?[/quote]

Not right now, that’s something we’re exploring though. Sorry for the trouble.

I’m using Ubuntu 12.04 with jre1.7.0_21 and the designer seems to launch OK with the following:

javaws "http://gatewayIP:8088/main/system/launch/designer/designer.jnlp"

I’ve got this in a shortcut and it seems to want to install another shortcut (which doesn’t work, of course), but you can trash that after the first time.

Hope this helps.

I hit this same problem and am glad to see its not just my system, is there a way to modify the .jnlp file on the server side so that the client automatically downloads the file with the offending bits of code removed rather than having to save it locally, modify it and then execute?

Upgrade Java to the latest shoudl fix these issues

The native client launchers were created partially to get around JNLP problems like this. They are available in 7.5.11 and 7.6.4 releases, and use straight Java instead of Java Web Start (which get frequently broken by Oracle breaking JWS for Linux and OSX).

FYI:

I found that Java Web Start doesn’t work with Java update 45 (1.7.0_45), but does work the latest version Java update 51 ( 1.7.0_51).