# Frequent "Clock drift, degraded performance, or pause-the-world detected" (1-26 s) and wrapper "JVM appears hung" restarts on 8.1.54, low CPU, GC looks healthy

**URL:** <https://forum.inductiveautomation.com/t/frequent-clock-drift-degraded-performance-or-pause-the-world-detected-1-26-s-and-wrapper-jvm-appears-hung-restarts-on-8-1-54-low-cpu-gc-looks-healthy/117879>\
**Category:** Ignition\
**Tags:** gateway, perspective\
**Created:** [November 18, 2026, 5:45am UTC](https://forum.inductiveautomation.com/t/frequent-clock-drift-degraded-performance-or-pause-the-world-detected-1-26-s-and-wrapper-jvm-appears-hung-restarts-on-8-1-54-low-cpu-gc-looks-healthy/117879 "2026-11-18T05:45:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sudharsanan\_Mothilal](https://avatars.discourse-cdn.com/v4/letter/s/ac91a4/32.png) [@Sudharsanan\_Mothilal](https://forum.inductiveautomation.com/u/Sudharsanan_Mothilal)\
**Post date:** [November 18, 2026, 5:45am UTC](https://forum.inductiveautomation.com/t/frequent-clock-drift-degraded-performance-or-pause-the-world-detected-1-26-s-and-wrapper-jvm-appears-hung-restarts-on-8-1-54-low-cpu-gc-looks-healthy/117879/1 "2026-11-18T05:45:57Z")

</div>

Hi all,

Our 8.1.54 gateway (Linux VM, 10 vCPU, 19 GB RAM, `-Xmx12288m`) logs frequent **"Clock drift, degraded performance, or pause-the-world detected"** warnings (1-9 s), and the wrapper restarted it 3 times in 10 days with **"JVM appears hung"**.

**What we see:**

- CPU stays low (5-15%) during the pauses.
- No Full GCs; young GCs average ~100 ms.
- About 400 MB of the Java process is in Linux swap.
- Thread count keeps growing (744 → 1,123 in 4 days), mostly idle `pool-N-thread-M` threads.
- Many Perspective warnings: `Received prop sync for missing view` (up to 60,000/day).
- Drift gets worse with uptime and almost disappears right after a restart.
- Once the wrapper logged: `Wrapper Process has not received any CPU time for 13 seconds`.

**Questions:**

1. Is swapping the most likely cause, and should we set `vm.swappiness=1` or lower the heap (e.g. 8 GB)?
2. Can the "prop sync for missing view" warnings or the growing `pool-N` threads cause this?
3. What else should we check on the gateway?

Screenshots attached. Thanks!

 ![Screenshot 2026-11-18 111413](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/8/681b60c376176ceb3646792b19b3df2c021cc67a.png)

 ![Screenshot 2026-11-18 111353](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/f/0fd77467e0a06123ed2d7939b3b47ce166a42d9e.png)

---

<div class="post-metadata">

**Author:** ![tgarrison](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tgarrison/32/80965_2.png) [@tgarrison](https://forum.inductiveautomation.com/u/tgarrison)\
**Post date:** [November 18, 2026, 1:09pm UTC](https://forum.inductiveautomation.com/t/frequent-clock-drift-degraded-performance-or-pause-the-world-detected-1-26-s-and-wrapper-jvm-appears-hung-restarts-on-8-1-54-low-cpu-gc-looks-healthy/117879/2 "2026-11-18T13:09:07Z")

</div>

Those are some ugly graphs.

1. What's up with your CPU usage? A normal Ignition server will just run along for the most part at about 5-10%. All those spikes up over 50 and even up to 100% are likely problems.

2. Allocate less memory. It looks like you're really only using about 6G, so maybe 8G allocation (and be sure to set initial the same as max). Overallocating isn't good, espeically since it appears you allocated ALL the memory that the machine has, to Ignition. Java WILL eat it all.

3. Is it a VM? and if so, are those resources dedicated to the VM, or are they shared with other VMs? (they need to be dedicated).

4. Also, that memory chart is ugly for that garbage collection. It should generally be a nice sawtooth (climbing to your max mem, and then cleaning up). Once you fix 2, that may help that.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [November 18, 2026, 1:50pm UTC](https://forum.inductiveautomation.com/t/frequent-clock-drift-degraded-performance-or-pause-the-world-detected-1-26-s-and-wrapper-jvm-appears-hung-restarts-on-8-1-54-low-cpu-gc-looks-healthy/117879/3 "2026-11-18T13:50:37Z")

</div>

> [@Sudharsanan\_Mothilal](#):
>
> - Once the wrapper logged: `Wrapper Process has not received any CPU time for 13 seconds`.

This is very suspicious. Possibly a runnable thread storm in Ignition, but I would look at other processes in this server outside Ignition.
