Affects: Release Notes Date of First Response: 2010-07-08 12:25:05 Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000003hTBx&sfdc.override=1 project_key: JBEWS https://issues.apache.org/bugzilla/show_bug.cgi?id=48735 "after a failed worker has recovered, no request is fowarded to it although it is marked as OK in balancer-manager"
Help Desk Ticket Reference: Removed: https://access.redhat.com/issue-tracker/1053563 Added: https://c.na7.visual.force.com/apex/Case_View?id=500A0000003hTBx&sfdc.override=1
Release Notes Docs Status: Added: Not Yet Documented Writer: Added: rebecca_newton
We'll check if this is in the latest httpd that we update to, if not, we can apply the patch attached to the Apache BZ.
The reporter of the ASF BZ confirmed that this is not reproducible in httpd 2.2.17, and that's what we're upgrading to in EWS 1.0.2, so I'm marking this as resolved.
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue Release Notes Text: Added: No request is forwarded to a worker node after it has failed, even though it is marked as available in the balance manager. This issue has been resolved with the inclusion of httpd 2.2.17.
Unfortunately it IS reproducible in httpd 2.2.17. ASF somehow forgot to include their patch in 2.2.17. Is it possible to include the patch in EWS 1.0.2?
Can you please point me to a patch for this issue for 2.2.17? CR1 is to be handed off today, there's not enough time to rebuild and incorporate that into all the brew and hudson builds today, would it be ok to have this included in CR2?
Permaine, can you please reopen this bug? I could not seem to do it. Although it displays a couple of warnings, the patch posted in the ASF BZ does just a fine job for 2.2.17 as well. Here are the warnings: [szivan@manipura httpd-2.2.17]$ patch -p1 < ../httpd-2.2.16.patch patching file modules/proxy/mod_proxy.c Hunk #1 succeeded at 1038 (offset 22 lines). patching file modules/proxy/mod_proxy.h patching file modules/proxy/mod_proxy_balancer.c Hunk #4 succeeded at 623 with fuzz 2 (offset 9 lines). Hunk #5 succeeded at 848 (offset 9 lines). Hunk #6 succeeded at 880 (offset 9 lines). Hunk #7 succeeded at 1057 (offset 9 lines). Hunk #8 succeeded at 1140 (offset 9 lines). Hunk #9 succeeded at 1222 (offset 9 lines). After building the server with this patch it fixed the problem. If you prefer a patch built for 2.2.17, I will attach it in a minute.
this patch was made for 2.2.17 to solve the issue
Attachment: Added: httpd-2.2.17-busyness.patch
Reopening for incorporation in CR2.
Thanks for the patch, Ivan!
httpd22-2.2.17-9.ep5.el4 httpd-2.2.17-9.2.ep5.el6 httpd-2.2.17-9.1.ep5.el5 Built with the fix, will be in CR2.
Mladen, can you please update the Hudson build to use httpd-2_2_17-9_1_ep5_el5 and apply the patch for this issue (httpd-2.2.17-bz48735.patch)? Thanks!
Marking it as resolved as Hudson machines are working properly now, will be in CR2.
Release Notes Docs Status: Removed: Documented as Resolved Issue Writer: Removed: rebecca_newton Release Notes Text: Removed: No request is forwarded to a worker node after it has failed, even though it is marked as available in the balance manager. This issue has been resolved with the inclusion of httpd 2.2.17.