Solves issue with SendWorker failing because it cannot start a Thread…

… when constructing a connection pool. This solution is to do away with the connection pool. Since we are only ever using the ConnectionManager with a single thread (which is then discarded) there is no problem with multi threaded interference.

src/main/java/org/acra/util/HttpRequest.java

@@ -34,7 +34,7 @@
 import org.apache.http.entity.StringEntity;
 import org.apache.http.impl.auth.BasicScheme;
 import org.apache.http.impl.client.DefaultHttpClient;
-import org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager;
+import org.apache.http.impl.conn.SingleClientConnManager;
 import org.apache.http.params.BasicHttpParams;
 import org.apache.http.params.HttpConnectionParams;
 import org.apache.http.params.HttpParams;
@@ -211,7 +211,7 @@ private HttpClient getHttpClient() {
             registry.register(new Scheme("https", SSLSocketFactory.getSocketFactory(), 443));
         }
 
-        final ClientConnectionManager clientConnectionManager = new ThreadSafeClientConnManager(httpParams, registry);
+        final ClientConnectionManager clientConnectionManager = new SingleClientConnManager(httpParams, registry);
         final DefaultHttpClient httpClient = new DefaultHttpClient(clientConnectionManager, httpParams);
 
         final HttpRequestRetryHandler retryHandler = new SocketTimeOutRetryHandler(httpParams, maxNrRetries);