# Ignition Upgrade JVM Issue

**URL:** <https://forum.inductiveautomation.com/t/ignition-upgrade-jvm-issue/81249>\
**Category:** Ignition\
**Created:** [October 31, 2023, 5:26pm UTC](https://forum.inductiveautomation.com/t/ignition-upgrade-jvm-issue/81249 "2023-10-31T17:26:43Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![OscarJ](https://avatars.discourse-cdn.com/v4/letter/o/e8c25b/32.png) [@OscarJ](https://forum.inductiveautomation.com/u/OscarJ)\
**Post date:** [October 31, 2023, 5:26pm UTC](https://forum.inductiveautomation.com/t/ignition-upgrade-jvm-issue/81249/1 "2023-10-31T17:26:43Z")

</div>

When updating from version 8.1.25 to 8.1.33 we get an error when starting the gateway. The logs show an error in the JVM. Has anything similar happened to anyone?

[wrapper.txt](https://forum.inductiveautomation.com/uploads/short-url/nHGj7iyELSBQXYMpnvq4pXfQfp.txt) (196.6 KB)

---

<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 31, 2023, 5:29pm UTC](https://forum.inductiveautomation.com/t/ignition-upgrade-jvm-issue/81249/2 "2023-10-31T17:29:21Z")

</div>

Can you upload your `ignition.conf`? It looks like you may have some old and now invalid JVM params specified.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 31, 2023, 5:32pm UTC](https://forum.inductiveautomation.com/t/ignition-upgrade-jvm-issue/81249/3 "2023-10-31T17:32:34Z")

</div>

The primary one blowing up, `UseConcMarkSweepGC`, we attempted to automatically remove from the ignition.conf in an older version but can't prevent someone from manually adding it.  
That garbage collector implementation was deprecated in Java 9 and fully removed in Java 14; Ignition 8.1.33 moves the platform's Java version to 17, which is why it's now an issue.

---

<div class="post-metadata">

**Author:** ![OscarJ](https://avatars.discourse-cdn.com/v4/letter/o/e8c25b/32.png) [@OscarJ](https://forum.inductiveautomation.com/u/OscarJ)\
**Post date:** [October 31, 2023, 5:39pm UTC](https://forum.inductiveautomation.com/t/ignition-upgrade-jvm-issue/81249/4 "2023-10-31T17:39:19Z")

</div>

This is the ignition.conf  
[ignition.txt](https://forum.inductiveautomation.com/uploads/short-url/KE5O5Ehj0HWKYJa2sngEDzXPCG.txt) (8.7 KB)

---

<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 31, 2023, 5:43pm UTC](https://forum.inductiveautomation.com/t/ignition-upgrade-jvm-issue/81249/5 "2023-10-31T17:43:21Z")

</div>

Replace the whole "Java Additional Parameters" section with this:

```auto
# Java Additional Parameters
wrapper.java.additional.1=-Ddata.dir=data
wrapper.java.additional.2=--add-opens=java.base/java.lang=ALL-UNNAMED
wrapper.java.additional.3=--add-opens=java.base/java.security.cert=ALL-UNNAMED
wrapper.java.additional.4=--add-opens=java.base/java.util=ALL-UNNAMED
wrapper.java.additional.5=--add-opens=java.base/jdk.internal.misc=ALL-UNNAMED

```

---

<div class="post-metadata">

**Author:** ![OscarJ](https://avatars.discourse-cdn.com/v4/letter/o/e8c25b/32.png) [@OscarJ](https://forum.inductiveautomation.com/u/OscarJ)\
**Post date:** [October 31, 2023, 6:06pm UTC](https://forum.inductiveautomation.com/t/ignition-upgrade-jvm-issue/81249/6 "2023-10-31T18:06:54Z")

</div>

Thank you Kevin.  
In addition to that, I had to delete some data in the java.security file because it wouldn't let me connect to the database. Everything now works normally.

---

<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 31, 2023, 6:08pm UTC](https://forum.inductiveautomation.com/t/ignition-upgrade-jvm-issue/81249/7 "2023-10-31T18:08:09Z")

</div>

> [@OscarJ](#):
>
> In addition to that, I had to delete some data in the java.security file because it wouldn't let me connect to the database.

You'll have to do this anytime you upgrade and we happened to upgrade the JDK version as well. Ultimately you'll want to upgrade your janky old database that doesn't support modern TLS versions.