[JBoss JIRA] (MODCLUSTER-335) Regression in ProxyPass integration
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-335?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration updated MODCLUSTER-335:
-----------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=960243, https://bugzilla.redhat.com/show_bug.cgi?id=960246 (was: https://bugzilla.redhat.com/show_bug.cgi?id=960243)
> Regression in ProxyPass integration
> -----------------------------------
>
> Key: MODCLUSTER-335
> URL: https://issues.jboss.org/browse/MODCLUSTER-335
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.2.4.Final
> Environment: RHEL6 x86_64, the rest is to be confirmed...
> Reporter: Michal Babacek
> Assignee: Jean-Frederic Clere
> Fix For: 1.2.5.Final
>
> Attachments: logs-and-configs-m_c-1.2.3.zip, logs-and-configs-m_c-1.2.4.zip, test-run-modProxyOnlyPartOfUrlSpaceTest-mod_cluster-1.2.3.log, test-run-modProxyOnlyPartOfUrlSpaceTest-mod_cluster-1.2.4.log
>
>
> This configuration & test worked just fine with 1.2.3.Final and it is broken in 1.2.4.Final, so we have a *regression* here, I guess.
> {code}
> ProxyPassMatch ^/app/static/ !
> ProxyPass /app balancer://qacluster stickysession=JSESSIONID|jsessionid nofailover=on
> ProxyPass / !
> ProxyPassReverse /app balancer://qacluster
> ProxyPassReverseCookieDomain / /app/
> ProxyPassReverseCookiePath / /app/
> ProxyPreserveHost on
> {code}
> Accessing e.g. {{/app/clusterbench/requestinfo/}} returns HTTP 503. *requestinfo* comes from the famous [CommonRequestInfoServlet.java|https://github.com/Karm/clusterbench/blob/s...].
> h3. mod_cluster 1.2.3 ProxyPass test:
> *Failed tests*
> * modProxyOnlyPartOfUrlSpaceTest: Known fail: [JBQA-7899] Assert #10 Session ID must always be the same.
> * modProxyWithoutSessionId: Assert #1, fail, known as [MODCLUSTER-334], http://10.16.45.160:2080/clusterbench/requestinfo/ should have been available...
> h3. mod_cluster 1.2.4 ProxyPass test:
> *Failed tests*
> * modProxyOnlyPartOfUrlSpaceTest: Assert #1, fail, http://10.16.45.160:2080/app/clusterbench/requestinfo/ should have been available...
> * modProxyWithoutSessionId: Assert #1, fail, known as [MODCLUSTER-334], http://10.16.45.160:2080/clusterbench/requestinfo/ should have been available...
> What the test does is it accesses various URLs, getting either static content from httpd or a dynamic one from application server.
> Browse the attached files for complete configs, debug logs and test results. Ping me, if the zipped file structure does not make sense to you...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (MODCLUSTER-335) Regression in ProxyPass integration
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-335?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration updated MODCLUSTER-335:
-----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=960243
> Regression in ProxyPass integration
> -----------------------------------
>
> Key: MODCLUSTER-335
> URL: https://issues.jboss.org/browse/MODCLUSTER-335
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.2.4.Final
> Environment: RHEL6 x86_64, the rest is to be confirmed...
> Reporter: Michal Babacek
> Assignee: Jean-Frederic Clere
> Fix For: 1.2.5.Final
>
> Attachments: logs-and-configs-m_c-1.2.3.zip, logs-and-configs-m_c-1.2.4.zip, test-run-modProxyOnlyPartOfUrlSpaceTest-mod_cluster-1.2.3.log, test-run-modProxyOnlyPartOfUrlSpaceTest-mod_cluster-1.2.4.log
>
>
> This configuration & test worked just fine with 1.2.3.Final and it is broken in 1.2.4.Final, so we have a *regression* here, I guess.
> {code}
> ProxyPassMatch ^/app/static/ !
> ProxyPass /app balancer://qacluster stickysession=JSESSIONID|jsessionid nofailover=on
> ProxyPass / !
> ProxyPassReverse /app balancer://qacluster
> ProxyPassReverseCookieDomain / /app/
> ProxyPassReverseCookiePath / /app/
> ProxyPreserveHost on
> {code}
> Accessing e.g. {{/app/clusterbench/requestinfo/}} returns HTTP 503. *requestinfo* comes from the famous [CommonRequestInfoServlet.java|https://github.com/Karm/clusterbench/blob/s...].
> h3. mod_cluster 1.2.3 ProxyPass test:
> *Failed tests*
> * modProxyOnlyPartOfUrlSpaceTest: Known fail: [JBQA-7899] Assert #10 Session ID must always be the same.
> * modProxyWithoutSessionId: Assert #1, fail, known as [MODCLUSTER-334], http://10.16.45.160:2080/clusterbench/requestinfo/ should have been available...
> h3. mod_cluster 1.2.4 ProxyPass test:
> *Failed tests*
> * modProxyOnlyPartOfUrlSpaceTest: Assert #1, fail, http://10.16.45.160:2080/app/clusterbench/requestinfo/ should have been available...
> * modProxyWithoutSessionId: Assert #1, fail, known as [MODCLUSTER-334], http://10.16.45.160:2080/clusterbench/requestinfo/ should have been available...
> What the test does is it accesses various URLs, getting either static content from httpd or a dynamic one from application server.
> Browse the attached files for complete configs, debug logs and test results. Ping me, if the zipped file structure does not make sense to you...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (MODCLUSTER-335) Regression in ProxyPass integration
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-335?page=com.atlassian.jira.pl... ]
Michal Babacek updated MODCLUSTER-335:
--------------------------------------
Attachment: logs-and-configs-m_c-1.2.4.zip
logs-and-configs-m_c-1.2.3.zip
test-run-modProxyOnlyPartOfUrlSpaceTest-mod_cluster-1.2.4.log
test-run-modProxyOnlyPartOfUrlSpaceTest-mod_cluster-1.2.3.log
Logs, configs and a relevant part of the test run log added (showing what URLs were accessed and when).
> Regression in ProxyPass integration
> -----------------------------------
>
> Key: MODCLUSTER-335
> URL: https://issues.jboss.org/browse/MODCLUSTER-335
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.2.4.Final
> Environment: RHEL6 x86_64, the rest is to be confirmed...
> Reporter: Michal Babacek
> Assignee: Jean-Frederic Clere
> Fix For: 1.2.5.Final
>
> Attachments: logs-and-configs-m_c-1.2.3.zip, logs-and-configs-m_c-1.2.4.zip, test-run-modProxyOnlyPartOfUrlSpaceTest-mod_cluster-1.2.3.log, test-run-modProxyOnlyPartOfUrlSpaceTest-mod_cluster-1.2.4.log
>
>
> This configuration & test worked just fine with 1.2.3.Final and it is broken in 1.2.4.Final, so we have a *regression* here, I guess.
> {code}
> ProxyPassMatch ^/app/static/ !
> ProxyPass /app balancer://qacluster stickysession=JSESSIONID|jsessionid nofailover=on
> ProxyPass / !
> ProxyPassReverse /app balancer://qacluster
> ProxyPassReverseCookieDomain / /app/
> ProxyPassReverseCookiePath / /app/
> ProxyPreserveHost on
> {code}
> Accessing e.g. {{/app/clusterbench/requestinfo/}} returns HTTP 503. *requestinfo* comes from the famous [CommonRequestInfoServlet.java|https://github.com/Karm/clusterbench/blob/s...].
> h3. mod_cluster 1.2.3 ProxyPass test:
> *Failed tests*
> * modProxyOnlyPartOfUrlSpaceTest: Known fail: [JBQA-7899] Assert #10 Session ID must always be the same.
> * modProxyWithoutSessionId: Assert #1, fail, known as [MODCLUSTER-334], http://10.16.45.160:2080/clusterbench/requestinfo/ should have been available...
> h3. mod_cluster 1.2.4 ProxyPass test:
> *Failed tests*
> * modProxyOnlyPartOfUrlSpaceTest: Assert #1, fail, http://10.16.45.160:2080/app/clusterbench/requestinfo/ should have been available...
> * modProxyWithoutSessionId: Assert #1, fail, known as [MODCLUSTER-334], http://10.16.45.160:2080/clusterbench/requestinfo/ should have been available...
> What the test does is it accesses various URLs, getting either static content from httpd or a dynamic one from application server.
> Browse the attached files for complete configs, debug logs and test results. Ping me, if the zipped file structure does not make sense to you...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (MODCLUSTER-335) Regression in ProxyPass integration
by Michal Babacek (JIRA)
Michal Babacek created MODCLUSTER-335:
-----------------------------------------
Summary: Regression in ProxyPass integration
Key: MODCLUSTER-335
URL: https://issues.jboss.org/browse/MODCLUSTER-335
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.2.4.Final
Environment: RHEL6 x86_64, the rest is to be confirmed...
Reporter: Michal Babacek
Assignee: Jean-Frederic Clere
Fix For: 1.2.5.Final
This configuration & test worked just fine with 1.2.3.Final and it is broken in 1.2.4.Final, so we have a *regression* here, I guess.
{code}
ProxyPassMatch ^/app/static/ !
ProxyPass /app balancer://qacluster stickysession=JSESSIONID|jsessionid nofailover=on
ProxyPass / !
ProxyPassReverse /app balancer://qacluster
ProxyPassReverseCookieDomain / /app/
ProxyPassReverseCookiePath / /app/
ProxyPreserveHost on
{code}
Accessing e.g. {{/app/clusterbench/requestinfo/}} returns HTTP 503. *requestinfo* comes from the famous [CommonRequestInfoServlet.java|https://github.com/Karm/clusterbench/blob/s...].
h3. mod_cluster 1.2.3 ProxyPass test:
*Failed tests*
* modProxyOnlyPartOfUrlSpaceTest: Known fail: [JBQA-7899] Assert #10 Session ID must always be the same.
* modProxyWithoutSessionId: Assert #1, fail, known as [MODCLUSTER-334], http://10.16.45.160:2080/clusterbench/requestinfo/ should have been available...
h3. mod_cluster 1.2.4 ProxyPass test:
*Failed tests*
* modProxyOnlyPartOfUrlSpaceTest: Assert #1, fail, http://10.16.45.160:2080/app/clusterbench/requestinfo/ should have been available...
* modProxyWithoutSessionId: Assert #1, fail, known as [MODCLUSTER-334], http://10.16.45.160:2080/clusterbench/requestinfo/ should have been available...
What the test does is it accesses various URLs, getting either static content from httpd or a dynamic one from application server.
Browse the attached files for complete configs, debug logs and test results. Ping me, if the zipped file structure does not make sense to you...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (MODCLUSTER-334) mod_cluster core when use ProxyPass / balancer://bal and CreateBalancers 1
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-334?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on MODCLUSTER-334:
----------------------------------------------------
Michal Babacek <mbabacek(a)redhat.com> made a comment on [bug 958991|https://bugzilla.redhat.com/show_bug.cgi?id=958991]
Well, yes, it is fixed in master. Target release being mod_cluster 1.2.5.Final.
It is not fixed in 1.2.4.Final though. This means this bug is present in EAP 6.1.0.ER6.
One has to add that code only if one is using "CreateBalancers 1" (mod_cluster.conf in conf.d, httpd configuration). User might want to have something like:
CreateBalancers 1
ProxyPass / balancer://qacluster
and it won't work. Workaround would be to have:
CreateBalancers 1
ProxyPass / balancer://qacluster stickysession=JSESSIONID|jsessionid
Of course, "qacluster" is an arbitrary name. Default value for ManagerBalancerName directive is "mycluster".
> mod_cluster core when use ProxyPass / balancer://bal and CreateBalancers 1
> --------------------------------------------------------------------------
>
> Key: MODCLUSTER-334
> URL: https://issues.jboss.org/browse/MODCLUSTER-334
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.2.4.Final
> Environment: Any
> Reporter: Jean-Frederic Clere
> Assignee: Jean-Frederic Clere
> Fix For: 1.2.5.Final
>
>
> Use something like:
> ProxyPass / balancer://neo5
> CreateBalancers 1
> When the first STATUS is received from a node using the balancer (neo5) httpd will dump a core.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months