# Java 6 unsigned entry in resource

**URL:** <https://forum.inductiveautomation.com/t/java-6-unsigned-entry-in-resource/15760>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [October 24, 2017, 1:19pm UTC](https://forum.inductiveautomation.com/t/java-6-unsigned-entry-in-resource/15760 "2017-10-24T13:19:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![systemparadox](https://avatars.discourse-cdn.com/v4/letter/s/b5e925/32.png) [@systemparadox](https://forum.inductiveautomation.com/u/systemparadox)\
**Post date:** [October 24, 2017, 1:19pm UTC](https://forum.inductiveautomation.com/t/java-6-unsigned-entry-in-resource/15760/1 "2017-10-24T13:19:01Z")

</div>

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:

```auto
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.

---

<div class="post-metadata">

**Author:** ![ryanjmclaughlin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryanjmclaughlin/32/4318_2.png) [@ryanjmclaughlin](https://forum.inductiveautomation.com/u/ryanjmclaughlin)\
**Post date:** [October 24, 2017, 1:25pm UTC](https://forum.inductiveautomation.com/t/java-6-unsigned-entry-in-resource/15760/2 "2017-10-24T13:25:54Z")

</div>

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](http://forum.inductiveautomation.com/t/java-version-client-sadness/14033/7):
>
> 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…

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [October 24, 2017, 2:21pm UTC](https://forum.inductiveautomation.com/t/java-6-unsigned-entry-in-resource/15760/3 "2017-10-24T14:21:23Z")

</div>

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