DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=35642>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35642 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO ------- Additional Comments From [EMAIL PROTECTED] 2005-07-16 22:22 ------- Horia, I was unable to reproduce the problem with JRE 1.4.2.8 & 1.5.0.4 on Linux FC4 and on WinXP with JRE 1.4.2.4. I always get a reasonable connect timeout against a non-existent IP. The problem appears to be specific to your environment, LAN, TCP/IP setup, JRE or something else. Fundamentally HttpClient does not do anything tricky. It just employs reflection to execute 1.4 specific methods: http://jakarta.apache.org/commons/httpclient/xref/org/apache/commons/httpclient/protocol/ReflectionSocketFactory.html#85 If you do not care about Java 1.2 compatibility, consider implementing a simpler ProtocolSocketFactory that directly calls 1.4 specific Socket methods and see if that makes any difference. http://jakarta.apache.org/commons/httpclient/xref/org/apache/commons/httpclient/protocol/DefaultProtocolSocketFactory.html#48 Once Odi's patch is committed we will not have much choice but to mark this bug as WORKSFORME unless we get more info how to reproduce the problem. Oleg -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
