# Gateway wrapper JVM ping timeout

**URL:** <https://forum.inductiveautomation.com/t/gateway-wrapper-jvm-ping-timeout/114703>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [March 26, 2026, 6:59pm UTC](https://forum.inductiveautomation.com/t/gateway-wrapper-jvm-ping-timeout/114703 "2026-03-26T18:59:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![paul.longtine](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul.longtine/32/10599_2.png) [@paul.longtine](https://forum.inductiveautomation.com/u/paul.longtine)\
**Post date:** [March 26, 2026, 6:59pm UTC](https://forum.inductiveautomation.com/t/gateway-wrapper-jvm-ping-timeout/114703/1 "2026-03-26T18:59:48Z")

</div>

Running Ignition 8.1.50, with _mostly_ the default `ignition.conf`.

We ran into something that caused the [wrapper ping timeout](https://wrapper.tanukisoftware.com/doc/english/prop-ping-timeout.html) to kick in and boot the JVM.

I believe this was triggered by accidentally looking at the "Threads" section under Diagnostics on a busy gateway... I was trying to look at the running scripts but my mouse hit the edge and clicked "Threads" instead.

Has anyone hit this before? Should the ping timeout be set differently?

---

<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:** [March 26, 2026, 7:05pm UTC](https://forum.inductiveautomation.com/t/gateway-wrapper-jvm-ping-timeout/114703/2 "2026-03-26T19:05:44Z")

</div>

On large busy systems, taking a thread dump is an extremely disruptive action. Consider making the ping timeout longer.