Bug 960243 – Regression in ProxyPass integration

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 960243 - Regression in ProxyPass integration

Summary:	Regression in ProxyPass integration

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	mod_cluster (Show other bugs)
Sub Component:
Version:	6.1.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	ER4
Target Release:	EAP 6.2.0
Assigned To:	Jean-frederic Clere
QA Contact:	Michal Karm Babacek
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2013-05-06 14:53 EDT by Michal Karm Babacek
Modified:	2013-12-15 11:22 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	A regression in an earlier version of mod_proxy_cluster.so (bug 960246) returned HTTP 503 errors when accessing a directory (for example <filename class="directory">/app/clusterbench/requestinfo/</filename>. This issue has been corrected in this release of JBoss EAP and mod_proxy_cluster.so now works as expected when accessing directories.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2013-12-15 11:22:21 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	MODCLUSTER-335	Major	Closed	Regression in ProxyPass integration	2015-07-01 07:19:24 EDT

Groups: None (edit)

Description Michal Karm Babacek 2013-05-06 14:53:17 EDT

https://issues.jboss.org/browse/MODCLUSTER-335

Comment 1 JBoss JIRA Server 2013-05-07 02:55:13 EDT

Jean-Frederic Clere <jfclere@jboss.org> made a comment on jira MODCLUSTER-335

I need the httpd.conf corresponding to the test and the error_log (with debug) to investigate the problem.

Comment 2 JBoss JIRA Server 2013-05-07 03:03:09 EDT

Michal Babacek <mbabacek@redhat.com> made a comment on jira MODCLUSTER-335

These are present in the zips I attached yesterday, sorry for not pointing it out explicitly.
Paths:

[^logs-and-configs-m_c-1.2.4.zip]
{{target-ER6/jboss-reports/logs-archive/noe.ews.modcluster.tests.ModProxyTest/modProxyOnlyPartOfUrlSpaceTest/HttpdRhel-2/ews-httpd/logs/error_log}}

{{target-ER6/jboss-reports/confs-archive/noe.ews.modcluster.tests.ModProxyTest/modProxyOnlyPartOfUrlSpaceTest/HttpdRhel-2/ews-httpd/mod_cluster.conf/mod_cluster.conf}}

{{target-ER6/jboss-reports/confs-archive/noe.ews.modcluster.tests.ModProxyTest/modProxyOnlyPartOfUrlSpaceTest/HttpdRhel-2/ews-httpd/proxy1.conf/proxy1.conf}}

{{target-ER6/jboss-reports/confs-archive/noe.ews.modcluster.tests.ModProxyTest/modProxyOnlyPartOfUrlSpaceTest/HttpdRhel-2/ews-httpd/httpd.conf/httpd.conf}}

Analogically in [^logs-and-configs-m_c-1.2.3.zip] but for having "target-ER5" instead of "target-ER6".

Comment 3 JBoss JIRA Server 2013-05-07 03:44:10 EDT

Jean-Frederic Clere <jfclere@jboss.org> made a comment on jira MODCLUSTER-335

Hm nothing more than logs in  /target-ER6/jboss-reports/logs-archive/noe.ews.modcluster.tests.ModProxyTest/modProxyOnlyPartOfUrlSpaceTest/HttpdRhel-2/ews-httpd/

Comment 4 JBoss JIRA Server 2013-05-07 07:39:00 EDT

Michal Babacek <mbabacek@redhat.com> made a comment on jira MODCLUSTER-335

I have confirmed the regression lays in *mod_proxy_cluster.so*, not in httpd itself or any other module.
With the same *httpd*, I was updating module by module from 1.2.3 to 1.2.4 with this result:

 * (x) mod_proxy_cluster.so  -- broken  
 * (/) mod_advertise.so  
 * (/) mod_manager.so  
 * (/) mod_slotmem.so  

I understand it does not look like so, but I can not find anything but this diff in [mod_proxy_cluster.c|https://gist.github.com/Karm/5530970] that would be even remotely relevant to the issue on hand.

Comment 5 JBoss JIRA Server 2013-05-07 08:05:40 EDT

Jean-Frederic Clere <jfclere@jboss.org> made a comment on jira MODCLUSTER-335

That is a regression from the fix of MODCLUSTER-328.

Comment 6 JBoss JIRA Server 2013-05-07 08:19:46 EDT

Jean-Frederic Clere <jfclere@jboss.org> made a comment on jira MODCLUSTER-335

Fixed by https://github.com/modcluster/mod_cluster/commit/6610301d2dfbf8d19b2f5edb0328a870eaf78d82

Comment 7 JBoss JIRA Server 2013-05-07 11:54:35 EDT

Michal Babacek <mbabacek@redhat.com> updated the status of jira MODCLUSTER-335 to Closed

Comment 8 JBoss JIRA Server 2013-05-07 11:54:35 EDT

Michal Babacek <mbabacek@redhat.com> made a comment on jira MODCLUSTER-335

Verified on [modcluster/mod_cluster/tree/1.2.x|https://github.com/modcluster/mod_cluster/tree/1.2.x]. Closing.

Comment 9 Jean-frederic Clere 2013-05-22 04:20:11 EDT

Cause: 

A bug in the logic that uses the uri to find the node to route the request uses the raw uri instead the one resulting of the ProxyPass directive. 

Consequence: 

ProxyPass/ProxyPassMatch won't work with mod_cluster.

Workaround (if any): 

None.

Result: 
.

Comment 12 Michal Karm Babacek 2013-08-27 10:08:36 EDT

It is fixed in m_c 1.2.5.

Comment 13 Michal Karm Babacek 2013-10-08 06:36:07 EDT

Cool now. m_c 1.2.6.Final / EAP 6.2.ER4

Comment 15 Scott Mumford 2013-11-20 16:26:08 EST

Added draft Doc Text (albeit a little light on the 'how' of the fix). Marking for inclusion in 6.2 Release Notes document.

Comment 16 Jean-frederic Clere 2013-11-22 05:51:55 EST

The directory is a bit weird...
The bug was triggered when having something like:
ProxyPass /myapp balancer://qacluster
in the configuration
and the effect was that request to /myapp where returning 503.

Note You need to log in before you can comment on or make changes to this bug.