I would just make 'stale' connection check optional and off per default. Making the check pluggable would require too much of a change for what is essentially a release candidate. That should be better done as a part of 3.0 redesign IMO.
I agree that removing isStale() by default certainly fixes the performance problem. However, it makes MTCM somewhat unstable. The case where stale connections do not cause errors until read from will throw unrecoverable exceptions. Is this an acceptable alternative?
We definitely should. I consider myself fairly knowledgeable about HttpClient internals, but I have to say this massage has caught me by surprise.
I would also consider you quite knowledgeable about HttpClient internals:) I will look to see what we can do here.
I would also really like to see a few more DEBUG logs to be added to the MultiThreadedHttpConnectionManager#doGetConnection method
Okay. Would you like to take care of this or should I?
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
