Apologies for the slow reply. Yes, I was suggesting you may be missing a call to HttpEntity.consumeContent() somewhere. That's what tripped me up.
If you've got a large codebase that would be difficult to sift through manually, I'd suggest creating a target server that can emulate different kinds of situations (dropping the connection half way through a response, throwing 404/500 errors, etc), and seeing if any of those occurring repeatedly trigger the connection counts to pile up. Hope this helps, Sam On 4 June 2010 22:06, Oleg Kalnichevski <[email protected]> wrote: > On Fri, 2010-06-04 at 10:58 -0700, Renaud Waldura wrote: >> Sam: >> >> I think you're on the right track. I've seen connection counters reach the >> set limit (400 in my case) -- and that point, everything just hangs. >> >> You're saying I might be missing call to HttpEntity.consumeContent() >> somewhere, right? >> >> Related question: what is "total issued connections", and how does it >> compare to "total allocated connections"? >> > > Total issued connections = total number of connections leased from the > pool and in active use. > > Total kept-alive connections = total number of connections kept in the > pool that are currently idle (not used). > > Total allocated connections = issued + kept-alive. > > Feel free to suggest better terms if these seem confusing. > > Cheers > > Oleg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
