# Mobile Module: - Login issues

**URL:** <https://forum.inductiveautomation.com/t/mobile-module-login-issues/8181>\
**Category:** Ignition\
**Created:** [March 20, 2014, 12:10am UTC](https://forum.inductiveautomation.com/t/mobile-module-login-issues/8181 "2014-03-20T00:10:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kevin.keefe](https://avatars.discourse-cdn.com/v4/letter/k/bcef8e/32.png) [@kevin.keefe](https://forum.inductiveautomation.com/u/kevin.keefe)\
**Post date:** [March 20, 2014, 12:10am UTC](https://forum.inductiveautomation.com/t/mobile-module-login-issues/8181/1 "2014-03-20T00:10:38Z")

</div>

Hi  
I’m having an issue with the mobile module which I cannot see to get sorted so any advice would be grateful.  
The system is running Server 2008 Standard.  
Ignition is version 7.6.4. (Latest release)  
Java is version 7 update 25.

When trying to log into the mobile app via an iPad we are confronted with a " java.net.SocketException: Connection reset by peer. Socket write error"

The console is giving the following information: -

[size=85]11:22:33 PM DataServlet Failure in mobiledata/initvm

java.net.SocketException: Connection reset by peer: 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.sendMessage(MobileVMManager.java:595)  
at com.inductiveautomation.mobile.gateway.MobileVMManager.initializeVM(MobileVMManager.java:337)  
at com.inductiveautomation.mobile.gateway.servlets.MobileSession.initializeVM(MobileSession.java:384)  
at com.inductiveautomation.mobile.gateway.servlets.MobileDataServlet$InitVM.handle(MobileDataServlet.java:835)  
at com.inductiveautomation.mobile.gateway.servlets.MobileDataServlet.doRequest(MobileDataServlet.java:159)  
at com.inductiveautomation.mobile.gateway.servlets.MobileDataServlet.doGet(MobileDataServlet.java:108)  
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)  
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)  
at com.inductiveautomation.ignition.gateway.bootstrap.MapServlet.service(MapServlet.java:85)  
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)  
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)  
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)  
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)  
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)  
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)  
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)  
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)  
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606)  
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)  
at java.lang.Thread.run(Unknown Source)

less  
(I) 11:22:33 PM ClientVM Client vm d42aa7ab-6254-8bf0-5b2a-5b4cb66c18c1 closed: Exception during init message[/size]

It doesn’t seem to happen every time and once reset the system will log in fine.

I have trawled the forums and tried everything that has been said before but all to no avail.  
Any ideas?

Kev

---

<div class="post-metadata">

**Author:** ![kevin.keefe](https://avatars.discourse-cdn.com/v4/letter/k/bcef8e/32.png) [@kevin.keefe](https://forum.inductiveautomation.com/u/kevin.keefe)\
**Post date:** [March 20, 2014, 9:55am UTC](https://forum.inductiveautomation.com/t/mobile-module-login-issues/8181/2 "2014-03-20T09:55:07Z")

</div>

We have upgraded to Java7 Update 51, but this has had had no impact on the fault

Kev