You should really contact support.
At a glance, it sounds like your underlying system is simply overwhelmed. The big telltale are messages like this:
2022-02-23 00:16:33:000
Pinging the JVM took 28 seconds to respond.
2022-02-23 00:16:33:000
Pinging the JVM took 23 seconds to respond.
2022-02-23 00:16:33:000
Pinging the JVM took 18 seconds to respond.
2022-02-23 00:16:33:000
Pinging the JVM took 13 seconds to respond.
2022-02-23 00:16:33:000
Pinging the JVM took 8 seconds to respond.
2022-02-23 00:17:09:000
JVM appears hung: Timed out waiting for signal from JVM. Restarting JVM.
2022-02-23 00:17:10:000
JVM exited after being requested to terminate.
These are being logged semi-frequently by the ‘service wrapper’ (the long-lived process that actually starts Ignition) and indicate that the IPC between the wrapper and Ignition itself is failing. That’s pretty unusual outside of severe resource starvation issues.
How’s the CPU usage of this server? Is it a dedicated physical server, or a virtual machine? If it’s a VM, how are its resources allocated compared to the host/what else is the VM host running?
I would generally recommend not having SQL server (or any other RDBMS) on the same server as Ignition. DBs and Ignition both tend to ‘compete’ pretty strongly for resources like CPU time and memory.