Ignition likes to restart on its own

Ignition has restarted a few times over the last few weeks, I have the following error in the log. Any help troubleshooting would be appreciated, thanks!

ERROR | wrapper | 2014/12/11 07:43:15 | JVM appears hung: Timed out waiting for signal from JVM. ERROR | wrapper | 2014/12/11 07:43:15 | JVM did not exit on request, terminated DEBUG | wrapperp | 2014/12/11 07:43:16 | socket read failed. (An existing connection was forcibly closed by the remote host. (0x2746)) DEBUG | wrapperp | 2014/12/11 07:43:16 | Closing backend socket. DEBUG | wrapper | 2014/12/11 07:43:16 | Preparing to restart with mode 2. DEBUG | wrapper | 2014/12/11 07:43:16 | Waiting 5 seconds before launching another JVM. STATUS | wrapper | 2014/12/11 07:43:20 | Reloading Wrapper configuration... DEBUG | wrapper | 2014/12/11 07:43:20 | Working directory set to: C:\Program Files\Inductive Automation\Ignition DEBUG | wrapper | 2014/12/11 07:43:20 | Working directory set to: C:\Program Files\Inductive Automation\Ignition DEBUG | wrapper | 2014/12/11 07:43:20 | Working directory set to: C:\Program Files\Inductive Automation\Ignition DEBUG | wrapperp | 2014/12/11 07:43:21 | server listening on port 32000. DEBUG | wrapper | 2014/12/11 07:43:21 | Magic number for file C:\Program Files\Java\jre1.8.0_25\bin\java.exe: 0x4d5a9000 DEBUG | wrapper | 2014/12/11 07:43:21 | Ping settings: wrapper.ping.interval=5, wrapper.ping.interval.logged=1, wrapper.ping.timeout=30 DEBUG | wrapperp | 2014/12/11 07:43:21 | socket not open, so packet not sent LOGFILE : logs\wrapper.log DEBUG | wrapper | 2014/12/11 07:43:21 | active log file changed: logs\wrapper.log STATUS | wrapper | 2014/12/11 07:43:21 | Launching a JVM... DEBUG | wrapper | 2014/12/11 07:43:21 | Command: "C:\Program Files\Java\jre1.8.0_25\bin\java.exe" -XX:PermSize=64m -XX:MaxPermSize=128m -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled -Ddata.dir=data -Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false -Dfile.encoding=Cp1252 -Duser.language=en -Xms256m -Xmx2048m -Djava.library.path="lib" -classpath "lib/wrapper.jar;lib/catapult.jar" -Dwrapper.key="StrhL6PrFt-T2eYbzpKiETpuc2IYDPv7" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" -Dwrapper.pid=7264 -Dwrapper.version="3.5.15-st" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=2 -Dwrapper.lang.domain=wrapper org.tanukisoftware.wrapper.WrapperSimpleApp com.inductiveautomation.catapult.Catapult DEBUG | wrapper | 2014/12/11 07:43:21 | JVM started (PID=1264) INFO | jvm 2 | 2014/12/11 07:43:24 | WrapperManager Debug: WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoader@5c647e05 INFO | jvm 2 | 2014/12/11 07:43:24 | WrapperManager: Initializing... INFO | jvm 2 | 2014/12/11 07:43:24 | WrapperManager Debug: JVM #2 INFO | jvm 2 | 2014/12/11 07:43:24 | WrapperManager Debug: Running a 64-bit JVM.

Can you attach the rest of your logs here?

I don’t see anything in the logs aside from some slow query warnings. The only thing I can think of is to see if you’re running anywhere near whatever the max memory you’ve allocated for Ignition is. Or if you’re running on a virtual machine make sure the host isn’t over-provisioned.

If neither of those pan out you might have to run this one through support so they can look at your system.