Mobile Client launch problem in 7.8

Mobile client problem in 7.8 version, below error occurs.
“java.lang.Exception: Timeout waiting for new VM.”

Java 7 installed.

Java path : “C:\Program Files\Java\jre7\bin\java.exe”

Both Ignition 7.7 and Ignition 7.8 require Java 8 for the machine running the gateway - you might start there.

Thanks,

7.7 and 7.8 both require Java 8, it is correct but think mobile client works fine with Java 7. This information provided by Ignition support team. So previously with version 7.7, I am using java 8 and java 7 for mobile client.

Same thing I had tried with version 7.8.

Initially without installing java 7, I had tried mobile client with version 7.8 and found mobile client not working. So I had installed java 7 and tried using full path of java 7 but mobile client is not working and found “java.lang.Exception: Timeout waiting for new VM.” error.

Could you please confirm that mobile client is working without java 7 ?

Today, I have done the fresh installation of Ignition 7.8 ( 7.8.0-beta1 (b2015090915) ) and JAVA 8 (Oracle Corporation 1.8.0_60).

I have created new project for testing the Mobile Client.

While launching the mobile client from launch link provided on home page below error occurs.

Please suggest.



Please see below logs.

4:00:42 PM RectsB64 Failure in mobiledata/rects. [isClientVMRunning()=false, VM.id=8e6501b7-b029-d8d1-ca41-6cc673ee29fa

java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
at java.io.BufferedOutputStream.flush(Unknown Source)
at java.io.DataOutputStream.flush(Unknown Source)
at com.inductiveautomation.mobile.gateway.MobileVMManager$ClientVMImpl.getDirtyRectangles(MobileVMManager.java:493)
at com.inductiveautomation.mobile.gateway.servlets.MobileSession.getDirtyRectangles(MobileSession.java:323)
at com.inductiveautomation.mobile.gateway.servlets.MobileDataServlet$RectsBase64.handle(MobileDataServlet.java:327)
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:769)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1125)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1059)
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:97)
at org.eclipse.jetty.server.Server.handle(Server.java:497)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:248)
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:610)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:539)
at java.lang.Thread.run(Unknown Source)

less

(I) 4:00:42 PM ClientVM Client vm 8e6501b7-b029-d8d1-ca41-6cc673ee29fa closed: IOException during rectangle message: java.net.SocketException: Software caused connection abort: socket write error
(I) 4:00:42 PM VMManager New client VM discovered. id=8e6501b7-b029-d8d1-ca41-6cc673ee29fa
(I) 4:00:41 PM VMManager VMCreator starting 1 new client VM(s).
4:00:39 PM RectsB64 Failure in mobiledata/rects.

javax.servlet.ServletException: Session not initialized.
at com.inductiveautomation.mobile.gateway.servlets.MobileDataServlet.getSession(MobileDataServlet.java:588)
at com.inductiveautomation.mobile.gateway.servlets.MobileDataServlet.getSession(MobileDataServlet.java:571)
at com.inductiveautomation.mobile.gateway.servlets.MobileDataServlet$RectsBase64.handle(MobileDataServlet.java:325)
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:769)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1125)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1059)
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:97)
at org.eclipse.jetty.server.Server.handle(Server.java:497)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:248)
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:610)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:539)
at java.lang.Thread.run(Unknown Source)

Would this gateway happen to be running on a headless linux?

If so, refer to this:

https://support.inductiveautomation.com/index.php?/Knowledgebase/Article/View/33/0/running-the-mobile-module-on-linux

Upgrading Ignition might have written over your Ignition.sh if you had made this fix in a previous version.

Thanks,

The gateway running on Windows 7 (64bit) OS.

Mobile in Ignition 7.8 requires Java 8.

There is a known issue with running mobile on Ignition 7.8 and I am showed it is resolved for the stable release of 7.8.0.

I’m running 7.8.2 and I still have this issue… anyone found a solution? as you can see I had to restart 6 times and after that finally I made a successful connection. this it the only thing stopping me from using the mobile project right now. any help would be appreciated.
Sometimes it works the first try sometimes it doesn’t… I really don’t know whats going on. :scratch:

1 Like

Practically the same
I’m running 7.9.9 I tryed to restart mobile project several times and after that finally I made a successful connection. any help would be appreciated.
Sometimes it works the first try sometimes it doesn’t…

I have installed Java 8_191 (16 Oct 2018)

Hmm… this is odd, this issue was fixed in 7.9.8 if I’m not mistaken. I haven’t had this happen to me in a while.

1 Like

I have solved this problem by clearing cookies when my IE shutdown

IE? what are you trying to use the mobile project on a PC?

Yes, I have to use IE11 as a client on customer`s PCs for some time . “Clearing cookies when my IE shutdown” in my post should be read as “Delete browsing history on exit” in IE Properties. When tip is enabled I establish communication immediately.