RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

When ProxyErrorOverride is On, modcluster return  503 status code on subsequent requests, for about a second before returning 200 status code

Version-Release number of selected component (if applicable):

mod_cluster : 1.2.6.Final  and 1.2.11.Final 
Version jboss EAP : 6.1.1
Version apache httpd : 2.2.15
Version OS : RHEL 6.4
How reproducible:


Steps to Reproduce:
Customer provided a sample app to reproduce.

1. setup mod_cluster and deploy the sample app
2. run the test script, which curl to the sample app. 
3. Observe access and error log

Actual results:
we see around 10 calls after the error, getting 503 while, they should go through

Expected results:

After the broken call, all subsequent unbroken calls should return 200 status


Additional info:

Created attachment 1129209 [details]
reproducer

You might find this helpful:
See https://bugzilla.redhat.com/show_bug.cgi?id=1309598#c3
And https://bugzilla.redhat.com/show_bug.cgi?id=1309598#c5

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0784.html

*** Bug 1450298 has been marked as a duplicate of this bug. ***