July 2010 - mod_cluster-issues - Jboss List Archives

[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, 1 month

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, 1 month

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, 1 month

2
5
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, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-173) Alias max length too low

by Gregory Lardiere (JIRA)

Alias max length too low ------------------------ Key: MODCLUSTER-173 URL: https://jira.jboss.org/browse/MODCLUSTER-173 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.3.GA Environment: Windows server 2008 Reporter: Gregory Lardiere Assignee: Jean-Frederic Clere We have virtual-hosts in server.xml with aliases of more than 40 characters. No problem on the jboss side, but on apache side, mod_cluster fails with the following message : "MEM: Can't read host alias". Changing HOSTALIASZ from 40 to 64 (mod_clustersize.h) resolves the problem (see patch #1). NB: I had to fix a few "NMAKEmakefile", otherwise it won't compile with Visual Studio 2010 (see patch #2) -- 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, 4 months

4
11
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-115) mod_cluster Manual Technical Review

by Gary Meintjes (JIRA)

mod_cluster Manual Technical Review ----------------------------------- Key: MODCLUSTER-115 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-115 Project: mod_cluster Issue Type: Task Environment: JBoss AS Reporter: Gary Meintjes Assignee: Patrick Macdonald Patrick, Please assign someone perform a technical review on this mod_cluster publication as discussed. The link to the publication is: http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_App... Many thanx, Gary Meintjes -- 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, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-182) mod_cluster logs "[error] [client <ip>] proxy: error processing body" when the client ends the connection prematurely

by Samuel Mendenhall (JIRA)

mod_cluster logs "[error] [client <ip>] proxy: error processing body" when the client ends the connection prematurely --------------------------------------------------------------------------------------------------------------------- Key: MODCLUSTER-182 URL: https://jira.jboss.org/browse/MODCLUSTER-182 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.3.GA Reporter: Samuel Mendenhall Assignee: Jean-Frederic Clere In mod_jk when the client closes the connection unexpedtedly the following error log messages are produced: [Fri Jul 30 12:08:26 2010] [error] [client <ip>] proxy: error processing body [Fri Jul 30 12:08:26 2010] [error] proxy: dialog to 192.168.0.1:8009 (192.168.0.1) failed These messages should be logged as [warn] not error. -- 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, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-169) Demo client throws Bus Error when run with JDK 1.6 on OSX

by Bob McWhirter (JIRA)

Demo client throws Bus Error when run with JDK 1.6 on OSX --------------------------------------------------------- Key: MODCLUSTER-169 URL: https://jira.jboss.org/browse/MODCLUSTER-169 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.CR3 Environment: OSX 10.6.3 java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02-279-10M3065) Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01-279, mixed mode) Reporter: Bob McWhirter Assignee: Jean-Frederic Clere Priority: Minor Using the run-demo.sh results in a Bus Error when using JDK6 on OSX. Explicitly invoking JDK5 causes the client to launch without problem. -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-165) Better no servers connected message

by Jim Tyrrell (JIRA)

Better no servers connected message ----------------------------------- Key: MODCLUSTER-165 URL: https://jira.jboss.org/browse/MODCLUSTER-165 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.0.3.GA Environment: All Reporter: Jim Tyrrell Assignee: Jean-Frederic Clere The default landing screen before any jboss servers have connected is very thin. It would be nice to see a splash screen to have the ability to see that everything is installed correctly, but it is not yet listening or farming any content to the JBoss server instances. -- 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, 9 months

2
19
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-141) Use versioned docs

by Paul Ferraro (JIRA)

Use versioned docs ------------------ Key: MODCLUSTER-141 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-141 Project: mod_cluster Issue Type: Task Affects Versions: 1.1.0.CR1 Reporter: Paul Ferraro Assignee: Jean-Frederic Clere Priority: Minor Trying to maintain one copy of the documentation for multiple versions simultaneously is proving to be a pain in the @ss... Magnolia is very cumbersome as a documentation tool because of its treatment of "paragraphs", especially with respect to code fragments (of which our docs have many). I recommend we keep all of the documentation in subversion (using doxia, docbook or similar) so that it is versioned along with the source code. The download page would contain links to the docs along side binary and source distributions. This seems to be how most jboss.org projects are setup. -- 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, 9 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues July 2010