Start a new topic

Ping never reports a timeout even when the httptransport does report it....

Hi


Ping doesn't invoke the onFailure of the KinveyPIngCallback even when the socket timed out. In fact neither the onFailure or the onSuccess of the callback gets called and so the call to Ping essentiall. At the HTTPTransport layer though there is already a SocketTimeoutException happening which though doesn't get propagated to the callback resulting in Ping never returning any status via the callback:


W/HttpTransport(15758): java.net.SocketTimeoutException: Read timed out

W/HttpTransport(15758):  at org.apache.harmony.xnet.provider.jsse.NativeCrypto.SSL_read(Native Method)

W/HttpTransport(15758):  at org.apache.harmony.xnet.provider.jsse.OpenSSLSocketImpl$SSLInputStream.read(OpenSSLSocketImpl.java:664)

W/HttpTransport(15758):  at libcore.io.Streams.readSingleByte(Streams.java:41)

W/HttpTransport(15758):  at org.apache.harmony.xnet.provider.jsse.OpenSSLSocketImpl$SSLInputStream.read(OpenSSLSocketImpl.java:648)

W/HttpTransport(15758):  at libcore.io.Streams.readAsciiLine(Streams.java:201)

W/HttpTransport(15758):  at libcore.net.http.HttpEngine.readResponseHeaders(HttpEngine.java:573)

W/HttpTransport(15758):  at libcore.net.http.HttpEngine.readResponse(HttpEngine.java:821)

W/HttpTransport(15758):  at libcore.net.http.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:283)

W/HttpTransport(15758):  at libcore.net.http.HttpURLConnectionImpl.getResponseCode(HttpURLConnectionImpl.java:495)

W/HttpTransport(15758):  at libcore.net.http.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:134)

W/HttpTransport(15758):  at com.google.api.client.http.javanet.NetHttpResponse.<init>(NetHttpResponse.java:37)

W/HttpTransport(15758):  at com.google.api.client.http.javanet.NetHttpRequest.execute(NetHttpRequest.java:94)

W/HttpTransport(15758):  at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:964)

W/HttpTransport(15758):  at com.kinvey.java.core.AbstractKinveyClientRequest.executeUnparsed(AbstractKinveyClientRequest.java:333)

W/HttpTransport(15758):  at com.kinvey.java.core.AbstractKinveyClientRequest.executeUnparsed(AbstractKinveyClientRequest.java:297)

W/HttpTransport(15758):  at com.kinvey.java.core.AbstractKinveyClientRequest.execute(AbstractKinveyClientRequest.java:370)

W/HttpTransport(15758):  at com.kinvey.java.offline.AbstractKinveyOfflineClientRequest.offlineFromService(AbstractKinveyOfflineClientRequest.java:129)

W/HttpTransport(15758):  at com.kinvey.java.offline.OfflinePolicy$1.execute(OfflinePolicy.java:42)

W/HttpTransport(15758):  at com.kinvey.java.offline.AbstractKinveyOfflineClientRequest.execute(AbstractKinveyOfflineClientRequest.java:155)

W/HttpTransport(15758):  at com.kinvey.android.AsyncAppData$SaveRequest.executeAsync(AsyncAppData.java:623)

W/HttpTransport(15758):  at com.kinvey.android.AsyncClientRequest.doInBackground(AsyncClientRequest.java:71)

W/HttpTransport(15758):  at android.os.AsyncTask$2.call(AsyncTask.java:287)

W/HttpTransport(15758):  at java.util.concurrent.FutureTask.run(FutureTask.java:234)

W/HttpTransport(15758):  at com.kinvey.android.AsyncClientRequest$KinveySerialExecutor$1.run(AsyncClientRequest.java:145)

W/HttpTransport(15758):  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)

W/HttpTransport(15758):  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)

W/HttpTransport(15758):  at java.lang.Thread.run(Thread.java:856)


 

Thanks

Pankaj


Pankaj,  


This issue has been fixed and will be released with the next version of the java library,  which should be within the next week or so.


Thanks for reporting this issue,

Pankaj,


Thank you for reporting this bug, we will look into it shortly and I will be in touch about the status of this issue.


Thanks,

Login or Signup to post a comment