Ignition Gateway (7.7.2) clientlauncher Problem

Hi everyone,

I have this Ignition Gateway 7.7.2 installed in my local system. This version requires to have java 8 version installed. When I tried to launch my application using ‘clientlauncher’ it didn’t showed. I suspected that this issue is somewhat related to the java version installed in my system, so when I’ve checked the Gateway Java Detection it says: Ignition was unable to automatically detect what version of the Javatm Platform is installed on your computer. Please ensure that Java 6 or Java 7 is installed

Does this mean that ‘clientlauncher’ requires java 7 or 6 installed to use it? why not using java 8 or latest version instead?

This will be a problem if you have java 8 on both Server and Client system with using ‘clientlauncher’ to launch each application.

Anyone can help us on this?

Thanks.

What operating system are you using?

I assume you are referring to clientlauncher.exe? It definitely runs with Java 8, so that is not an issue. Also, the Gateway Java detection doesn’t always pick up the Java version on the local system, so I would ignore that. If you are using clientlauncher.exe, check /.ignition/clientlauncher-data/clientlauncher.log for any errors.

I'm using Windows 7 x64.

@mgross, yes that's what I'm reffering to. You are right that the clientlauncher will run but the project didn't launched at all. I'll be checking on the log if there are some errors thrown in there.

Thanks for the response.

@mgross, sorry for the late reply. Here’s what I’ve got in the log file after I tried again to launch an application. It still not showing up.

[color=#0000FF]WARN [ClientLauncher ] [18:16:37,234]: multicast.addr was not specified! A default value of 231.1.1.1 will be used.
WARN [ClientLauncher ] [18:16:37,234]: multicast.receive.port was not specified! A default value of 4446 will be used.
WARN [ClientLauncher ] [18:16:37,235]: timeoutsecs was not specified! A default timeout of 30 seconds will be used.
WARN [ClientLauncher ] [18:16:37,235]: retries was not specified! A default retry count of -1 will be used, meaning that the Client Launcher will retry indefinitely.
WARN [ClientLauncher ] [18:16:37,235]: The screen property is missing from the launch parameters. It will default to screen ‘0’.
WARN [ClientLauncher ] [18:16:37,235]: The windowmode property is missing from the launch parameters. It will default to ‘window’ (non-full-screen) mode.

INFO [ClientLauncher ] [18:16:37,236]: launch.xml does not exist. Creating one now.
INFO [SplashFrame ] [18:17:11,757]: Downloading “http://10.81.67.164:8088/main/system/launchbin/launchclient.jar” (timeout=30)…
INFO [SplashFrame ] [18:17:11,761]: Starting download of 2503345 bytes
INFO [GatewayCommUtil ] [18:17:13,640]: Downloading “http://10.81.67.164:8088/main/system/images/APC%20Icon/CE_048.png” (timeout=30)…
INFO [GatewayCommUtil ] [18:17:13,643]: Starting project image download of 2073 bytes
INFO [GatewayCommUtil ] [18:17:13,646]: Downloading “http://10.81.67.164:8088/main/system/images/ConfigEditor/icon_256.png” (timeout=30)…
INFO [GatewayCommUtil ] [18:17:13,651]: Starting project image download of -1 bytes
INFO [GatewayCommUtil ] [18:17:13,655]: Downloading “http://10.81.67.164:8088/main/system/images/RMS/icon_048.png” (timeout=30)…
INFO [GatewayCommUtil ] [18:17:13,660]: Starting project image download of 2178 bytes
INFO [GatewayCommUtil ] [18:17:13,679]: Downloading “http://10.81.67.164:8088/main/system/images/APC%20Icon/RS_048.png” (timeout=30)…
INFO [GatewayCommUtil ] [18:17:13,682]: Starting project image download of 2178 bytes
INFO [ClientLauncherFrame ] [18:17:22,921]: Starting Java with the following parameters:java -classpath C:\Users\dlaki7130346.ignition\clientlauncher-data\launchclient.jar -Djavaws.sr.gateway.addr.0=10.81.67.164:8088/main -Djavaws.sr.scope=C -Djavaws.sr.launchts=1429179433188 -Djavaws.sr.main=com.inductiveautomation.factorypmi.application.runtime.ClientLaunchHook -Xms32M -Xmx256M -XX:MaxPermSize=128m -Dsun.java2d.d3d=false -Djavaws.sr.project=ConfigEditorTest -Djavaws.sr.screen=0 com.inductiveautomation.ignition.client.launch.BootstrapSwing [/color]

Ok, so the issue is that the client itself is not starting. The next step is to run that Java command at the end of the log in a terminal, like so:

java -classpath C:\Users\dlaki7130346\.ignition\clientlauncher-data\launchclient.jar -Djavaws.sr.gateway.addr.0=10.81.67.164:8088/main -Djavaws.sr.scope=C -Djavaws.sr.launchts=1429179433188 -Djavaws.sr.main=com.inductiveautomation.factorypmi.application.runtime.ClientLaunchHook -Xms32M -Xmx256M -XX:MaxPermSize=128m -Dsun.java2d.d3d=false -Djavaws.sr.project=ConfigEditorTest -Djavaws.sr.screen=0 com.inductiveautomation.ignition.client.launch.BootstrapSwing

Any exceptions that occur when starting the client will show up in the terminal.

Hi All,

Sorry for the late response. This issue had been solved after we updated/upgraded our Ignition Gateway from 7.7.2 to 7.7.4. All applications we have are now showing when using clientlauncher.exe.

Thanks for all the help.