Northern Captain Northern Captain - 4 months ago 23
Android Question

android httpclient hangs on second request to the server (connection timed out)

I'm struggling with the following problem:
My App makes sequence of requests to the http server using HttpClient. I use HttpPut for sending data to the server.
First request goes well and fast, second request hangs for 40 sec and then I catch Connection timed out exception. I'm trying to reuse my HttpClient and send second request through the same instance. If I create new HttpClient together with new ConnectionManager, then everything works fine.

Why is this happening? And how to fix it and do not create new HttpClient each time?

Thanks in advance.

Here is my code: (if I comment readClient = newHttpClient(readClient) in doPut, then the problem arises.

public class WebTest
private HttpClient readClient;
private SchemeRegistry httpreg;
private HttpParams params;

private URI url; //

protected HttpClient newHttpClient(HttpClient oldClient)
if(oldClient != null)

ClientConnectionManager cm = new SingleClientConnManager(params, httpreg);
return new DefaultHttpClient(cm, params);

protected String doPut(String data)
//Every time we need to send data, we do new connection
//with new ConnectionManager and close old one
readClient = newHttpClient(readClient);


String responseS = null;
HttpPut put = new HttpPut(url);
HttpEntity entity = new StringEntity(data, "UTF-8");
put.setHeader("Content-Type", "application/json; charset=utf-8");
put.setHeader("Accept", "application/json");
put.setHeader("User-Agent", "Apache-HttpClient/WebTest");

responseS = readClient.execute(put, responseHandler);
catch(IOException exc)
//error handling here
return responseS;

public WebTest()
httpreg = new SchemeRegistry();
Scheme sch = new Scheme("http", PlainSocketFactory.getSocketFactory(), 80);

params = new BasicHttpParams();
ConnPerRoute perRoute = new ConnPerRouteBean(10);
ConnManagerParams.setMaxConnectionsPerRoute(params, perRoute);
ConnManagerParams.setMaxTotalConnections(params, 50);
ConnManagerParams.setTimeout(params, 15000);
int timeoutConnection = 15000;
HttpConnectionParams.setConnectionTimeout(params, timeoutConnection);
// Set the default socket timeout (SO_TIMEOUT)
// in milliseconds which is the timeout for waiting for data.
int timeoutSocket = 40000;
HttpConnectionParams.setSoTimeout(params, timeoutSocket);

private ResponseHandler<String> responseHandler = new ResponseHandler<String>()
public String handleResponse(HttpResponse response)
throws ClientProtocolException, IOException
StatusLine statusLine = response.getStatusLine();
if (statusLine.getStatusCode() >= 300)
throw new HttpResponseException(statusLine.getStatusCode(),

HttpEntity entity = response.getEntity();
if(entity == null)
return null;

InputStream instream = entity.getContent();
return this.toString(entity, instream, "UTF-8");

public String toString(
final HttpEntity entity,
final InputStream instream,
final String defaultCharset) throws IOException, ParseException
if (entity == null)
throw new IllegalArgumentException("HTTP entity may not be null");

if (instream == null)
return null;
if (entity.getContentLength() > Integer.MAX_VALUE)
throw new IllegalArgumentException("HTTP entity too large to be buffered in memory");
int i = (int)entity.getContentLength();
if (i < 0)
i = 4096;
String charset = EntityUtils.getContentCharSet(entity);
if (charset == null)
charset = defaultCharset;
if (charset == null)

Reader reader = new InputStreamReader(instream, charset);

StringBuilder buffer=new StringBuilder(i);
char[] tmp = new char[1024];
int l;
while((l = != -1)
buffer.append(tmp, 0, l);
} finally

return buffer.toString();



Sounds strange, but I had the exact same problem. The app I was working on was making several successive requests to download a bunch of thumbnail images to display in a ListView, and after the second one it would hang as if there was a dead lock in the HttpClient code.

The strange fix that I found was to use AndroidHttpClient instead of DefaultHttpClient. As soon as I did this, and I tried a lot of stuff before going this route, it started working just fine. Just remember to call client.close() when you're done with the request.

AndroidHttpClient is described in the documentation as DefaultHttpClient with "reasonable default settings and registered schemes for Android". Since this was introduced in api level 8 (Android 2.2), I dug up the source to duplicate these "default settings" so that I could use it further back than that api level. Here is my code for duplicating the defaults and a helper class with a static method for safely closing it

public class HttpClientProvider {

    // Default connection and socket timeout of 60 seconds. Tweak to taste.
    private static final int SOCKET_OPERATION_TIMEOUT = 60 * 1000;

    public static DefaultHttpClient newInstance(String userAgent)
        HttpParams params = new BasicHttpParams();

        HttpProtocolParams.setVersion(params, HttpVersion.HTTP_1_1);
        HttpProtocolParams.setContentCharset(params, HTTP.DEFAULT_CONTENT_CHARSET);
        HttpProtocolParams.setUseExpectContinue(params, true);

        HttpConnectionParams.setStaleCheckingEnabled(params, false);
        HttpConnectionParams.setConnectionTimeout(params, SOCKET_OPERATION_TIMEOUT);
        HttpConnectionParams.setSoTimeout(params, SOCKET_OPERATION_TIMEOUT);
        HttpConnectionParams.setSocketBufferSize(params, 8192);

        SchemeRegistry schReg = new SchemeRegistry();
        schReg.register(new Scheme("http", PlainSocketFactory.getSocketFactory(), 80));
        schReg.register(new Scheme("https", SSLSocketFactory.getSocketFactory(), 443));
        ClientConnectionManager conMgr = new ThreadSafeClientConnManager(params, schReg);

        DefaultHttpClient client = new DefaultHttpClient(conMgr, params);

        return client;


And in another class...

public static void safeClose(HttpClient client)
    if(client != null && client.getConnectionManager() != null)