Hi, This is in reference to a bug I filed where HttpClient seemed to freeze when under heavy concurrent access. The bug was closed noting that I wasn't closing the connection in my test. This was true, however if I set the connection pool size to be much larger than the number of threads the problem never occurs. The pool comes close to filling up and then it cleans itself out.
What I'd like to know is - is there a case when the cleaner thread realizes it can clean these not-closed connections out? I can't reproduce this problem in the single-threaded case, and need to know more to be able to reproduce this and verify it has been fixed in our application. Thanks for your help, Neil Thier
