January 2011 - mod_cluster-issues

[JBoss JIRA] Created: (MODCLUSTER-119) AdvertiseBindAddress does not default to the 23364 port

by Radoslav Husar (JIRA)

AdvertiseBindAddress does not default to the 23364 port ------------------------------------------------------- Key: MODCLUSTER-119 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-119 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.2.GA Environment: Fedora 11 Reporter: Radoslav Husar Assignee: Jean-Frederic Clere Hello, it looks as though 1.0.2 GA does not pick the default value for AdvertiseBindAddress and listens on random port each time whereas the documentation claims it defaults to the same setup as the AS part default setup. The docs say: AdvertiseBindAddress IP:port: That is the address and port httpd is bind to send the multicast messages. This allow to specify an address on multi IP address boxes. Default: 0.0.0.0:23364 Here is the different starts/stops and ports, below the host config without ABA set. [rhusar@rhusar modcluster]$ netstat -lpn | grep http (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 0 :::8888 :::* LISTEN 19610/httpd udp 0 0 0.0.0.0:60958 0.0.0.0:* 19610/httpd [rhusar@rhusar modcluster]$ netstat -lpn | grep http (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 0 :::8888 :::* LISTEN 19648/httpd udp 0 0 0.0.0.0:34758 0.0.0.0:* 19648/httpd [rhusar@rhusar modcluster]$ netstat -lpn | grep http (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 0 :::8888 :::* LISTEN 19676/httpd udp 0 0 0.0.0.0:58988 0.0.0.0:* 19676/httpd <VirtualHost *:8888> KeepAliveTimeout 60 MaxKeepAliveRequests 0 ManagerBalancerName mycluster AdvertiseFrequency 5 # File a Jira - not in sync with docs # http://www.jboss.org/mod_cluster/native/config.html # AdvertiseBindAddress 0.0.0.0:23364 </VirtualHost> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
8
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-122) Advertise does not work on name-based virtual hosts

by Radoslav Husar (JIRA)

Advertise does not work on name-based virtual hosts --------------------------------------------------- Key: MODCLUSTER-122 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-122 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.2.GA Environment: RHEL 5.4 Reporter: Radoslav Husar Assignee: Jean-Frederic Clere If you use Apache httpd name-based virtual hosts on the server with multiple IPs (without explicit configuration parameter ServerAdvertise On http://hostname:port), advertise does not work and sends 0.0.0.0 IP address to the back-end. This is problem when you have back-end server on the physically another machine. Module should use ServerName from the VirtualHost configuration value in this case (or this case should be documented). Refer to official Apache 2.2 documentation for more information on Name-based Virtual Host Support http://httpd.apache.org/docs/2.2/vhosts/name-based.html Snip from mod_cluster docs: > ServerAdvertise On http://hostname:port: Tell the hostname and port to use. Only needed if the VirtualHost is not > defined correctly or when VirtualHost is not used. Sample configuration: <VirtualHost *:8888> ServerName perf10 ... </VirtualHost> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
12
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-124) Make mod_cluster manager tolerant to F5 page refresh when disabled context

by Radoslav Husar (JIRA)

Make mod_cluster manager tolerant to F5 page refresh when disabled context -------------------------------------------------------------------------- Key: MODCLUSTER-124 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-124 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.0.2.GA Reporter: Radoslav Husar Assignee: Jean-Frederic Clere Priority: Minor I ran into this and found it rather unfriendly, when I wanted to refresh the mod_cluster manager (mcm) server returned Error 500. This happens when the last command was operating with a node which is no longer in the list. For example disabling a context: http://jawa11:7777/mod_cluster-manager?nonce=a6302da7-faa0-4338-8d35-9a25... You can easily run into this since there is no clear way - a link - to get to the page without any parameters (supposingly following the Autorefresh link which is not always desired to turn it off). Thanks for considering! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
5
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-198) Can only rewrite from the root in httpd if there is a root context deployed in JBoss

by Samuel Mendenhall (JIRA)

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

13 years, 1 month

3
18
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-188) mod_cluster failover does not work for a /webappcontext when the / root context exists

by Samuel Mendenhall (JIRA)

mod_cluster failover does not work for a /webappcontext when the / root context exists -------------------------------------------------------------------------------------- Key: MODCLUSTER-188 URL: https://jira.jboss.org/browse/MODCLUSTER-188 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Beta1, 1.0.4.GA Reporter: Samuel Mendenhall Assignee: Jean-Frederic Clere Fix For: 1.0.5, 1.1.1.Final Let's say for example that /webapp and / is mapped in mod_cluster and there are two JBoss instances. If in one JBoss instance you undeploy the /webapp, you would expect mod_cluster to failover to the other JBoss instance. However, this is not the case, mod_cluster will instead select the lesser context, the root context / and service the request from /webapp on the / context. The logic only tests for ENABLE and DISABLE the STOP is not tested. The failover of a context will only work currently if / or any smaller path is not deployed -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-205) The windoze bundle don't have the default configuration

by Jean-Frederic Clere (JIRA)

The windoze bundle don't have the default configuration ------------------------------------------------------- Key: MODCLUSTER-205 URL: https://issues.jboss.org/browse/MODCLUSTER-205 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Final Environment: windows any archu Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 1.1.1.Final The default files aren't in the bundle so the install fails -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
6
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-206) httpd cores after graceful restart after the mod_cluster configuration is added

by Jean-Frederic Clere (JIRA)

httpd cores after graceful restart after the mod_cluster configuration is added ------------------------------------------------------------------------------- Key: MODCLUSTER-206 URL: https://issues.jboss.org/browse/MODCLUSTER-206 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Final, 1.0.6 Environment: any Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 1.0.7, 1.1.1.Final start httpd with mod_cluster configuration. add the configuration in httpd.conf restart httpd using graceful restart. httpd child processes will crash because the storage is not initialized in mod_manager.... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-207) Add support for system properties used in 1.0.x

by Paul Ferraro (JIRA)

Add support for system properties used in 1.0.x ----------------------------------------------- Key: MODCLUSTER-207 URL: https://issues.jboss.org/browse/MODCLUSTER-207 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 1.1.1.Final To ease 1.0.x -> 1.1.x upgrades, we should support the system properties used in the default mod_cluster-jboss-beans.xml ModClusterConfig bean. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-133) STATUS should retry the worker even if there was an error before.

by Jean-Frederic Clere (JIRA)

STATUS should retry the worker even if there was an error before. ----------------------------------------------------------------- Key: MODCLUSTER-133 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-133 Project: mod_cluster Issue Type: Bug Environment: any Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 1.1.0.CR1 Once an error occurs a STATUS should retry but the moment we have: +++ [Thu Feb 25 16:49:24 2010] [debug] ajp_header.c(687): ajp_read_header: ajp_ilink_received 09 [Thu Feb 25 16:49:24 2010] [debug] ajp_header.c(697): ajp_parse_type: got 09 [Thu Feb 25 16:49:24 2010] [debug] mod_proxy_ajp.c(540): proxy: Processing of request failed backend: 1, output: 0 [Thu Feb 25 16:49:24 2010] [error] proxy: dialog to 192.168.100.150:8009 (192.168.100.150) failed [Thu Feb 25 16:49:24 2010] [debug] proxy_util.c(2017): proxy: AJP: has released connection for (192.168.100.150) [Thu Feb 25 16:49:24 2010] [debug] mod_proxy_cluster.c(1118): proxy: byrequests balancer FAILED [Thu Feb 25 16:49:24 2010] [error] proxy: CLUSTER: (balancer://mycluster). All workers are in error state [Thu Feb 25 16:49:26 2010] [debug] mod_manager.c(1416): manager_trans STATUS (/) [Thu Feb 25 16:49:26 2010] [debug] mod_manager.c(1929): manager_handler STATUS (/) processing: "JVMRoute=node3&Load=78" [Thu Feb 25 16:49:26 2010] [debug] proxy_util.c(1937): proxy: ajp: retrying the worker for (192.168.100.150) [Thu Feb 25 16:49:26 2010] [error] proxy: ajp: disabled connection for (192.168.100.150) [Thu Feb 25 16:49:26 2010] [debug] mod_proxy_cluster.c(1333): proxy_cluster_isup: pingpong failed [Thu Feb 25 16:49:26 2010] [debug] mod_manager.c(1970): manager_handler STATUS OK [Thu Feb 25 16:49:36 2010] [debug] mod_manager.c(1416): manager_trans STATUS (/) [Thu Feb 25 16:49:36 2010] [debug] mod_manager.c(1929): manager_handler STATUS (/) processing: "JVMRoute=node3&Load=77" [Thu Feb 25 16:49:36 2010] [debug] proxy_util.c(1937): proxy: ajp: retrying the worker for (192.168.100.150) [Thu Feb 25 16:49:36 2010] [error] proxy: ajp: disabled connection for (192.168.100.150) +++ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
4
0 / 0

[JBoss JIRA] Updated: (MODCLUSTER-206) httpd cores after graceful restart after the mod_cluster configuration is added

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-206?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-206: ------------------------------------------- Workaround Description: Don't do that use a stop and start. (was: Don't do that :D) > httpd cores after graceful restart after the mod_cluster configuration is added > ------------------------------------------------------------------------------- > > Key: MODCLUSTER-206 > URL: https://issues.jboss.org/browse/MODCLUSTER-206 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.0.6, 1.1.0.Final > Environment: any > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.0.7, 1.1.1.Final > > > start httpd with mod_cluster configuration. > add the configuration in httpd.conf > restart httpd using graceful restart. > httpd child processes will crash because the storage is not initialized in mod_manager.... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues January 2011