Start a new topic

Network errors while saving entities

Hi,


I'm saving entities with the last version of the Android SDK (2.9.2) but I have a lot of network errors :

 

java.net.ProtocolException: unexpected end of stream
            at com.android.okhttp.internal.http.HttpConnection$FixedLengthSink.close(HttpConnection.java:303)
            at com.android.okio.RealBufferedSink.close(RealBufferedSink.java:174)
            at com.android.okio.RealBufferedSink$1.close(RealBufferedSink.java:142)
            at com.google.api.client.http.javanet.NetHttpRequest.execute(NetHttpRequest.java:81)
            at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:965)
            at com.kinvey.java.core.AbstractKinveyClientRequest.executeUnparsed(AbstractKinveyClientRequest.java:397)
            at com.kinvey.java.core.AbstractKinveyClientRequest.executeUnparsed(AbstractKinveyClientRequest.java:357)
            at com.kinvey.java.core.AbstractKinveyClientRequest.execute(AbstractKinveyClientRequest.java:466)
            at com.kinvey.java.offline.AbstractKinveyOfflineClientRequest.offlineFromService(AbstractKinveyOfflineClientRequest.java:130)
            at com.kinvey.java.offline.OfflinePolicy$1.execute(OfflinePolicy.java:42)
            at com.kinvey.java.offline.AbstractKinveyOfflineClientRequest.execute(AbstractKinveyOfflineClientRequest.java:156)
            at com.kinvey.android.AsyncAppData$SaveRequest.executeAsync(AsyncAppData.java:625)
            at com.kinvey.android.AsyncClientRequest.doInBackground(AsyncClientRequest.java:71)
            at android.os.AsyncTask$2.call(AsyncTask.java:292)
            at java.util.concurrent.FutureTask.run(FutureTask.java:237)
            at com.kinvey.android.AsyncClientRequest$KinveySerialExecutor$1.run(AsyncClientRequest.java:145)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
            at java.lang.Thread.run(Thread.java:818)

 

Or :

 

java.net.ProtocolException: expected 233 bytes but received 234
            at com.android.okhttp.internal.http.HttpConnection$FixedLengthSink.write(HttpConnection.java:288)
            at com.android.okio.RealBufferedSink.close(RealBufferedSink.java:167)
            at com.android.okio.RealBufferedSink$1.close(RealBufferedSink.java:142)
            at com.google.api.client.http.javanet.NetHttpRequest.execute(NetHttpRequest.java:81)
            at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:965)
            at com.kinvey.java.core.AbstractKinveyClientRequest.executeUnparsed(AbstractKinveyClientRequest.java:397)
            at com.kinvey.java.core.AbstractKinveyClientRequest.executeUnparsed(AbstractKinveyClientRequest.java:357)
            at com.kinvey.java.core.AbstractKinveyClientRequest.execute(AbstractKinveyClientRequest.java:466)
            at com.kinvey.java.offline.AbstractKinveyOfflineClientRequest.offlineFromService(AbstractKinveyOfflineClientRequest.java:130)
            at com.kinvey.java.offline.OfflinePolicy$1.execute(OfflinePolicy.java:42)
            at com.kinvey.java.offline.AbstractKinveyOfflineClientRequest.execute(AbstractKinveyOfflineClientRequest.java:156)
            at com.kinvey.android.AsyncAppData$SaveRequest.executeAsync(AsyncAppData.java:625)
            at com.kinvey.android.AsyncClientRequest.doInBackground(AsyncClientRequest.java:71)
            at android.os.AsyncTask$2.call(AsyncTask.java:292)
            at java.util.concurrent.FutureTask.run(FutureTask.java:237)
            at com.kinvey.android.AsyncClientRequest$KinveySerialExecutor$1.run(AsyncClientRequest.java:145)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
            at java.lang.Thread.run(Thread.java:818)

 

I'm not sure but I does not have the problem with an old version of the Kinvey Android lib.


Fabreax,


Can you check to see if you are still getting that type of error now?  We had a minor disruption this morning which may have affected a portion of users save operations.  


Thanks,

It seems to be ok. Thanks !

Login or Signup to post a comment