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=44334>. 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=44334 ------- Additional Comments From [EMAIL PROTECTED] 2008-02-02 08:50 ------- You are correct that there is bug here, but the bug is different from what you expect. mod_proxy_balancer should not even try to sent the failed request to a different member of the cluster. This is because: 1. A POST request is non idempotent and thus it is not allowed to resend it without user confirmation once its sending had started (RFC2616 8.1.4 / 9.1.2). 2. Your request contains a request body. httpd handles request bodies as streams and does not store them. This means once it has sent it to a Tomcat it is gone and cannot be sent again to another Tomcat as httpd does not have its data available any longer. This is now fixed in trunk by r617822 (http://svn.apache.org/viewvc?rev=617822 &view=rev). Nevertheless the problem you see will persist even with this patch. The only possibility to avoid this would be waiting to connect / send headers until there is request body data available, but this does not make sense for most other people. So I fear the only solution to your problem is to increase the value for connectionTimeout on Tomcat to something like 4 seconds or to fix your client to send the request body immediately. -- 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]
