Hi,
I am having the same “Timeout waiting on new VM” issue with 7.8.1 that was referenced as resolved in the thread below below… Any insight? A trace log is attached and my version info is below, thank you in advance for any assistance you can provide!
Current versions:
Ignition - 7.8.1
Java - 1.8.0_73
Vision - 8.8.1
Mobile - 3.8.1
Old thread:
https://inductiveautomation.com/forum/viewtopic.php?f=72&t=14444&hilit=timeout+waiting+for+new+VM
Trace log below, the file I tried to upload evidently was not attached…
9:48:59 AM DataServlet Failure in mobiledata/initvm
java.lang.Exception: Timeout waiting for new VM.
at com.inductiveautomation.mobile.gateway.servlets.MobileSession.initializeVM(MobileSession.java:455)
at com.inductiveautomation.mobile.gateway.servlets.MobileDataServlet$InitVM.handle(MobileDataServlet.java:880)
at com.inductiveautomation.mobile.gateway.servlets.MobileDataServlet.doRequest(MobileDataServlet.java:182)
at com.inductiveautomation.mobile.gateway.servlets.MobileDataServlet.doGet(MobileDataServlet.java:131)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at com.inductiveautomation.ignition.gateway.bootstrap.MapServlet.service(MapServlet.java:85)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:816)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1156)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1088)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:119)
at org.eclipse.jetty.server.Server.handle(Server.java:517)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:306)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:242)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:245)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:75)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:213)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:147)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
at java.lang.Thread.run(Unknown Source)
less
9:48:59 AM VMManager Timed-out waiting for new client VM. (Waited for 10 seconds)
9:48:58 AM VMManager Client VM exited unexpectedly with code 1.
(D) 9:48:58 AM VMManager Starting vm: java -cp C:\Program Files\Inductive Automation\Ignition\lib\core\launch\launchclient.jar;C:\Program Files\Inductive Automation\Ignition\data\mobile_wdir\mobile-common.jar;C:\Program Files\Inductive Automation\Ignition\data\mobile_wdir\mobile-client-bootstrap.jar -Dmobile.callback.interface=localhost -Dmobile.callback.port=45900 -DWebEncodingSocket.throttleThreshold=150 -Xmx256M com.inductiveautomation.mobile.MobileMain
(I) 9:48:58 AM VMManager VMCreator starting 1 new client VM(s).
Mobile client settings have to be changed to the file path for Java 8 on the gateway.
We also had to up the Client memory to 512MB