Java 6 unsigned entry in resource

[systemparadox]

We are currently upgrading Ignition from 7.8.3 to 7.9.4. It’s working for users with Java 8, but users with Java 6 are getting the following error when trying to start a client:

Unable to launch the application.

com.sun.deploy.net.JARSigningException: Found unsigned entry in resource: http://ignition:80/main/system/launchbin/launchclient.jar

These users are not able to upgrade Java due to other legacy applications. What can be done to resolve this issue? At this point I’m not sure if this is a bug in Ignition, a gateway configuration issue or a client Java configuration issue.

Any help would be much appreciated.

Thanks.

[ryanjmclaughlin]

Java 6 turned into a nightmare for us. I switched to the Native Client launcher and bundled java with it so there is no system dependency on needing a java install. I push out the client with our corporate software deployment system. Much easier.

Java version client sadness

So I spent some time with the application installer builder InnoScript. It’s not bad and fairly straight forward. Basically I build an installer that will put the client launcher in the ProgramData folder along with a custom launch.xml with the gateway name and a JRE folder with 32 or 64bit JRE depending on the client arch. Additionally, the install puts a link in AllUsers Start Menu to Ignition Applications which points to the clientlauncher.exe [image] The installer can run graphically or…

[Kevin.Herron]

You need to use the Native Client Launcher to continue using Java 6.