I've looked in Bugzilla and the list archives to find a comparable issue, but have been unsuccessful at finding a similar circumstance. If someone recognizes the problem and has an implementation solution, I would be very grateful for any suggestions you could provide.
I'm experiencing a problem with the response code (and body) returned after HttpClient tries to execute a (get) method on an unknown host. If the host had previously been in DNS and returned a valid (200, eg) response code, subsequent attempts to execute still return that same code and body, although the host is actually unavailable. All instances of the client object will continue to return the same 200 response until the servlet container has been restarted; after the restart, the client does throw the expected unknown host exception. Alternatively, if the first execution of a get method returns the unknown host error, further attempts to execute return that same exception, even after the host has DNS restored. Again, restarting Tomcat/JRun 'fixes' the return code. I have implemented the client code in both Tomcat 4 on Linux (Redhat) (as a struts action servlet) and JRun 3 on Windows 2000 (as a jsp servlet), with the same results. Turning on trace and logging has not afforded any insights into the problem. Please let me know if this description does not make any sense, or code/logs would be helpful (hopefully, this problem sounds familiar to someone, and I've simply done something wrong in my code).
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
