Hi my Ignition gateway is stuck in a faulted spiral and I'm not sure how to bring it back. Included is my wrapper.log.
wrapper.log (3.9 MB)
This:
INFO | jvm 1 | 2026/04/24 10:18:59 | E [IgnitionGateway ] [15:18:59]: Error during context startup.
INFO | jvm 1 | 2026/04/24 10:18:59 | java.util.ConcurrentModificationException: null
INFO | jvm 1 | 2026/04/24 10:18:59 | at java.base/java.util.HashMap$ValueSpliterator.forEachRemaining(Unknown Source)
INFO | jvm 1 | 2026/04/24 10:18:59 | at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
INFO | jvm 1 | 2026/04/24 10:18:59 | at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
INFO | jvm 1 | 2026/04/24 10:18:59 | at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(Unknown Source)
INFO | jvm 1 | 2026/04/24 10:18:59 | at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(Unknown Source)
INFO | jvm 1 | 2026/04/24 10:18:59 | at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)
INFO | jvm 1 | 2026/04/24 10:18:59 | at java.base/java.util.stream.ReferencePipeline.forEach(Unknown Source)
INFO | jvm 1 | 2026/04/24 10:18:59 | at com.inductiveautomation.ignition.gateway.alarming.status.AlarmStateModel.startup(AlarmStateModel.java:188)
INFO | jvm 1 | 2026/04/24 10:18:59 | at com.inductiveautomation.ignition.gateway.alarming.AlarmManagerImpl.startup(AlarmManagerImpl.java:180)
INFO | jvm 1 | 2026/04/24 10:18:59 | at com.inductiveautomation.ignition.gateway.IgnitionGateway.startupInternal(IgnitionGateway.java:1264)
INFO | jvm 1 | 2026/04/24 10:18:59 | at com.inductiveautomation.ignition.gateway.redundancy.RedundancyManagerImpl.startup(RedundancyManagerImpl.java:301)
INFO | jvm 1 | 2026/04/24 10:18:59 | at com.inductiveautomation.ignition.gateway.IgnitionGateway.initRedundancy(IgnitionGateway.java:759)
INFO | jvm 1 | 2026/04/24 10:18:59 | at com.inductiveautomation.ignition.gateway.IgnitionGateway.lambda$initInternal$0(IgnitionGateway.java:693)
INFO | jvm 1 | 2026/04/24 10:18:59 | at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$ThrowableCatchingRunnable.run(BasicExecutionEngine.java:544)
INFO | jvm 1 | 2026/04/24 10:18:59 | at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
INFO | jvm 1 | 2026/04/24 10:18:59 | at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
INFO | jvm 1 | 2026/04/24 10:18:59 | at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
INFO | jvm 1 | 2026/04/24 10:18:59 | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
INFO | jvm 1 | 2026/04/24 10:18:59 | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
INFO | jvm 1 | 2026/04/24 10:18:59 | at java.base/java.lang.Thread.run(Unknown Source)
is a bug. Probably exposed by the pathologically long tag subsystem startup. (9+ minutes)
You should open a support ticket. (You will almost certainly need to upgrade, presuming this is a known bug.)
This is indeed a known bug, fixed in 8.3.0. I asked the alarming team if there were plans to backport to 8.1, not sure yet what the answer is.
1 Like
Opening a support ticket is the correct way forward for this. 8.1 updates are going to be weeks out at the earliest and there are internal processes that are needed to justify them. Support is your best path forward to get this issue resolved.
2 Likes