Twitter4J

Eric Jensen added a comment - 15/Jun/10 11:42 AM I realized this is actually fixing a more serious bug with using the httpclient implementation than I thought. The original version does not pass a ConnectionManager to the DefaultHttpClient constructor, which as per http://hc.apache.org/httpcomponents-client/httpclient/apidocs/org/apache/http/impl/client/DefaultHttpClient.html results in using a SingleClientConnManager which is documented as "Even though this class is thread-safe it ought to be used by one execution thread only." even though twitter4j.Twitter is supposed to be safe for use with concurrent requests. Specifically, the behavior of SingleClientConnManager seems to be to force a close of any in-flight request if you make a concurrent one.

Yusuke Yamamoto added a comment - 13/Dec/10 11:29 PM total connection is set at HttpClientImpl:89         cm.setMaxTotal(conf.getHttpMaxTotalConnections()); and shutdown at :114         client.getConnectionManager().shutdown(); Please reopen if you still see any issue.