on 2011 Mar 31 9:03 AM
Hi
Sometimes my generic sync unexpectedly stops on the mobile client on a PDA.
I have a JSP-application running in IBrowse on Intermec PDA. I know the PDA is connected as I have a remote connection open at the same time I was testing this.
This is from the trace.txt, does anyone know what it mean?
D End: Dumping file /MI/sync/(SHARED)/out/package.out
I Outbound file size for user (SHARED) is 2038
P Do not use http proxy (system properties update)
P Use following gateway for synchronization: https://mobizcm2.yara.com:443
I GzipDataCompression: Gzip data compression is switched on
P Sending outbound file compressed to server.
P Outbound file was compressedly sent.
I HttpSynchronizer caught exception java.net.SocketException: Unexpected end of file from server
java.net.SocketException: Unexpected end of file from server
at com.sun.net.ssl.internal.www.protocol.https.HttpClient.b()
at com.sun.net.ssl.internal.www.protocol.https.HttpClient.a()
at com.sun.net.ssl.internal.www.protocol.https.HttpClient.b()
at com.sun.net.ssl.internal.www.protocol.https.HttpClient.a()
at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection.getInputStream()
at com.sap.ip.me.sync.HTTPSynchronizer.getInputStreamViaTimeOutOrNot()
at com.sap.ip.me.sync.HTTPSynchronizer.synchronize()
at com.sap.ip.me.sync.HTTPSynchronizer.synchronize()
at com.sap.ip.me.sync.HTTPSynchronizer.exchangeData()
at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle()
at com.sap.ip.me.sync.SyncManagerImpl.syncForUser()
at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization()
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()
at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()
at com.yara.industrial.yaraapp.sync.TestconnSynchronizationProvider.doSync()
at com.yara.industrial.yaraapp.bl.TestconnBl.checkConn()
at com.yara.industrial.yaraapp.sync.SyncHandling.Synchronize()
at com.yara.industrial.yaraapp.SyncServlet.doHandleEvent()
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGetThreadSafe()
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGet()
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doPost()
at javax.servlet.http.HttpServlet.service()
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.service()
at javax.servlet.http.HttpServlet.service()
at org.apache.tomcat.core.ServletWrapper.doService()
at org.apache.tomcat.core.Handler.service()
at org.apache.tomcat.core.ServletWrapper.service()
at org.apache.tomcat.core.ContextManager.internalService()
at org.apache.tomcat.core.ContextManager.service()
at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection()
at org.apache.tomcat.service.TcpWorkerThread.runIt()
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run()
at java.lang.Thread.run()
Regs
Øyvind
Hi,
if you are running HTTPS - then you should change the package size to small - or manually to a value smaller 800. This should cure the issue.
Regards,
Oliver
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
69 | |
11 | |
11 | |
10 | |
9 | |
8 | |
7 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.