[JBoss JIRA] Created: (MODCLUSTER-198) Can only rewrite from the root in httpd if there is a root context deployed in JBoss
10:05 a.m.
Can only rewrite from the root in httpd if there is a root context deployed in JBoss
------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://jira.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host: 192.168.235.128,Port:
8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 1,Ttl:
60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node balancer
NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node balancer
NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host: 192.168.235.128,Port:
8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 1,Ttl:
60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:05 a.m.
New subject: [JBoss JIRA] Updated: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://jira.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.plug...
]
Samuel Mendenhall updated MODCLUSTER-198:
-----------------------------------------
Summary: Can only rewrite from the root context in httpd if there is a root context
deployed in JBoss (was: Can only rewrite from the root in httpd if there is a root
context deployed in JBoss)
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://jira.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:21 p.m.
New subject: [JBoss JIRA] Updated: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://jira.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.plug...
]
Jean-Frederic Clere updated MODCLUSTER-198:
-------------------------------------------
Affects Version/s: 1.1.0.Final
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://jira.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:21 p.m.
New subject: [JBoss JIRA] Resolved: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://jira.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.plug...
]
Jean-Frederic Clere resolved MODCLUSTER-198.
--------------------------------------------
Resolution: Done
Fix by r427
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://jira.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:32 p.m.
New subject: [JBoss JIRA] Updated: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://issues.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere updated MODCLUSTER-198:
-------------------------------------------
Fix Version/s: 1.0.7
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://issues.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.7, 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:32 p.m.
New subject: [JBoss JIRA] Reopened: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://issues.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere reopened MODCLUSTER-198:
--------------------------------------------
Fix for 1.0.7 would be nice.
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://issues.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.7, 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:56 a.m.
New subject: [JBoss JIRA] Resolved: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://issues.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere resolved MODCLUSTER-198.
--------------------------------------------
Resolution: Done
Fix by r470
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://issues.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.7, 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:38 a.m.
New subject: [JBoss JIRA] Updated: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://issues.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere updated MODCLUSTER-198:
-------------------------------------------
Fix Version/s: 1.0.8
1.1.2.Final
(was: 1.1.1.Final)
(was: 1.0.7)
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://issues.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.8, 1.1.2.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:38 a.m.
New subject: [JBoss JIRA] Reopened: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://issues.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere reopened MODCLUSTER-198:
--------------------------------------------
The fix is broken (side effects)....
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://issues.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.8, 1.1.2.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:40 a.m.
New subject: [JBoss JIRA] Updated: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://issues.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere updated MODCLUSTER-198:
-------------------------------------------
Comment: was deleted
(was: The fix is broken (side effects)....)
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://issues.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.8, 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:40 a.m.
New subject: [JBoss JIRA] Updated: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://issues.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere updated MODCLUSTER-198:
-------------------------------------------
Fix Version/s: 1.1.1.Final
(was: 1.1.2.Final )
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://issues.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.8, 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:40 a.m.
New subject: [JBoss JIRA] Resolved: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://issues.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere resolved MODCLUSTER-198.
--------------------------------------------
Resolution: Done
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://issues.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.8, 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:45 a.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://issues.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.pl...
]
Laura Bailey commented on MODCLUSTER-198:
-----------------------------------------
Jean-Frederic, can you give a summary of why this problem occurred and what you did to fix
it for the release notes? At present all I have is:
mod_rewrite could not rewrite from the ROOT context in JBoss Enterprise Web Server if
there was no ROOT context deployed in JBoss Enterprise Application Platform.
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://issues.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.8, 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:56 a.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://issues.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere commented on MODCLUSTER-198:
------------------------------------------------
a better wording would be:
mod_rewrite could not rewrite from the / context in JBoss Enterprise Web Server if there
was no ROOT context deployed in JBoss Enterprise Application Platform.
In technical world thing like:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
only worked if a ROOT and sample context were deployed.
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://issues.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.8, 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:58 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://issues.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere edited comment on MODCLUSTER-198 at 2/24/11 3:57 AM:
-------------------------------------------------------------------------
a better wording would be:
mod_rewrite could not rewrite from the / context (in httpd) if there was no ROOT context
deployed in JBoss Enterprise Application Platform.
In technical world thing like:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
only worked if a ROOT and sample context were deployed.
was (Author: jfrederic.clere(a)jboss.com):
a better wording would be:
mod_rewrite could not rewrite from the / context in JBoss Enterprise Web Server if there
was no ROOT context deployed in JBoss Enterprise Application Platform.
In technical world thing like:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
only worked if a ROOT and sample context were deployed.
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://issues.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.8, 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:19 p.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://issues.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.pl...
]
Laura Bailey commented on MODCLUSTER-198:
-----------------------------------------
Thanks Jean-Frederic - updated JBPAPP-5511 with this.
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://issues.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.8, 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:21 p.m.
New subject: [JBoss JIRA] Updated: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://issues.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.pl...
]
Laura Bailey updated MODCLUSTER-198:
------------------------------------
Comment: was deleted
(was: Thanks Jean-Frederic - updated JBPAPP-5511 with this.)
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://issues.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.8, 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:21 p.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://issues.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.pl...
]
Laura Bailey commented on MODCLUSTER-198:
-----------------------------------------
Thanks Jean-Frederic, but I still need to know why this happened, what was done to fix it,
and how the user's experience changed.
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://issues.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.8, 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:02 a.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-198) Can only rewrite from the root context in httpd if there is a root context deployed in JBoss
[
https://issues.jboss.org/browse/MODCLUSTER-198?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere commented on MODCLUSTER-198:
------------------------------------------------
That was a bug in mod_cluster it used the original uri instead the one provided by
mod_rewrite.
Now it works the user doesn't need a "additional" ROOT context to have the
rewrite rule working.
Can only rewrite from the root context in httpd if there is a root
context deployed in JBoss
--------------------------------------------------------------------------------------------
Key: MODCLUSTER-198
URL: https://issues.jboss.org/browse/MODCLUSTER-198
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.8, 1.1.1.Final
See: http://community.jboss.org/thread/159462
====
I have a working mod_cluster 1.0.4 in front of EAP 5.1 (.com). I have been advised to use
mod_rewrite and it works well. But i'm curious about the following scenario:
mod_cluster set to expose ROOT. ROOT.war removed from JBoss. /sample deployed to jboss.
mod_cluster INFO looks like:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 88
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
When i do:
RewriteRule ^/sample/(.*)$ balancer://uat/sample/$1 [P,L]
and ask for my.url/sample/ it works perfectly.
If i do:
RewriteRule ^/(.*)$ balancer://uat/sample/$1 [P,L]
and go to my.url/ i get a 503 from apache and see
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(962): get_balancer_by_node
balancer NOT found
[Wed Dec 01 07:37:20 2010] [debug] mod_proxy_cluster.c(1137): proxy: byrequests balancer
FAILED
[Wed Dec 01 07:37:20 2010] [error] proxy: CLUSTER: (balancer://uat). All workers are in
error state
in the apache logs.
If i put ROOT.war back in, mod_cluster-manager INFO shows:
Node: [1],Name: redcloud:8009:jboss.web,Balancer: uat,Domain: ,Host:
192.168.235.128,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10000,Ping:
10000000,Smax: 1,Ttl: 60000000,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 92
Vhost: [1:1:1], Alias: localhost
Context: [1:1:1], Context: /sample, Status: ENABLED
Context: [1:1:2], Context: /, Status: ENABLED
and my.url/ works (and serves the sameple app under root context).
So, my question is has anyone seen this behavior with mod_cluster and mod_rewrite? I
don't mind having a "dummy" app in to make ROOT visible but i don't
necessarily want to have to.
====
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4805
days inactive
4889
days old
mod_cluster-issues@lists.jboss.org
18 comments
3 participants
participants (3)
-
Jean-Frederic Clere (JIRA) -
Laura Bailey (JIRA)
-
Samuel Mendenhall (JIRA)