On Tue, Aug 30, 2011 at 9:40 AM, Nathan <[email protected]> wrote: > After forcing some errors and doing some debugging, I found that I was not > always calling entity.consumecontent() if I got an error, as you suggested > in another thread. If an actual exception is thrown, I hope I don't have to. > Nonetheless, if I get a status code other than 200, there can still be > content. If I do not consume this content, the pool fills up and my thread > is frozen after about 6 failed requests. If I do consume said content, then > I can continue to get errors without deadlock.
You definitely want to close/consume your entities. Depending on how you intent to use the HttpClient though, you may run out of connections even if you do. The defaults (on GB) are max 2 connections per route and max 20 total, so you might want to tweak those if needed. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
