HttpClient execute keeps giving ConnectTimeoutException

Question

I have this very big bug in my application that I really can\'t seem to solve. Whenever I make a rest call via the following code:

  HttpGet request = new H         


        

Answer 1

The problem is the DefaultHttpClient. Are you using it asynchronously? Since the DefaultHttpClient is not thread-safe, using it in an asynchronous environment might cause a problem. I've had this problem before when my activity started multiple Http connection at the same time and i ended up changing it to use HttpURLConnection. You can refer to this site: http://www.vogella.de/articles/AndroidNetworking/article.html

Answer 2

I having the same issue.

Try using direct IP for your requests. I noticed that Android DNS lookups behave quite weird sometimes. I searched and found this : http://mailinglists.945824.n3.nabble.com/Android-and-reverse-DNS-lookup-issues-td3011461.html .

Dunno if it's relevant or not, i'm still trying to find a workaround. Maybe someone here can take a look and figure it out.

Answer 3

Had a similar issue, could be reproduced only when trying to connect using several devices simultaneously and the solution was:

Instance reboot solved problem with connections. (or just need to restart networking service)

(c) My server/instance admin

Also, there are people who experience similar issues and some other solutions worked for them, for instance:

1. Disable tcp_timestamp
2. Disable tcp_tw_reuse & tcp_tw_recycle
3. Enabled vm save mode in Android manifest: android:vmSafeMode="true"

---

• Android http connection - multiple devices cannot connect the same server
• https://developer.appcelerator.com/question/182935/httpclient-behaviour-ok-on-3g-but-faces-timeout-under-wifi-for-2-or-more-devices
• https://github.com/square/okhttp/issues/903
• https://github.com/square/okhttp/issues/1037
• https://github.com/square/okhttp/issues/1518

Answer 4

Check if you are able to connect using your development machine, Also check the load times. There is a very good chance your timeouts are way too small.