DO NOT REPLY [Bug 18893] - Endless loop in MultiThreadedHttpConnectionManager

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18893>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18893

Endless loop in MultiThreadedHttpConnectionManager

adrian@ephox.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From adrian@ephox.com  2003-04-10 07:01 -------
Hi,
Sorry I haven't managed to get back to you before now and save you some trouble,
been a busy day.

I passed on your query to the main HttpClient developers and received the
following reply from Mike Becke:

-----
This method looks a little suspicious at first I agree.  Though, as it turns out
the HttpException is only thrown when a connection wait timeout occurs.  In the
case of  getConnection(HostConfiguration) this will  never occur since we are
waiting indefinitely.  The try/catch/loop is just there to make the compiler
happy, and the LOG statement was added for completeness.  I have added a comment
detailing this to my latest patch for bug 18596.
-----

I'm personally still uncertain of exactly how the method structure works
(particularly why no IOException is ever thrown) but having seen Mike's
explanation and looked at the code again I'm satisfied that it won't go into an
infinite loop.

Again, sorry for not managing to get back to you sooner to save you the trouble
of filing this report, thanks for doing so and for the code scrutiny as well.