February 2012 - mod_cluster-issues

[JBoss JIRA] Created: (MODCLUSTER-253) ROOT in excludedContexts doesn't work

by Jean-Frederic Clere (JIRA)

ROOT in excludedContexts doesn't work ------------------------------------- Key: MODCLUSTER-253 URL: https://issues.jboss.org/browse/MODCLUSTER-253 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.3.Final Environment: 5.1.x Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 1.1.4.Final Just do: <property name="excludedContexts">ROOT,admin-console,invoker,jbossws,jmx-console,juddi,web-console</property> and see: [Thu Sep 01 10:12:07 2011] [debug] mod_manager.c(2296): manager_handler ENABLE-APP (/) processing: "JVMRoute=4e6189af-0502-3305-8ff3-fad7fee8b516&Alias=localhost&Context=%2F" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
12
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-187) ModClusterListener not working with Embedded Tomcat 6

by Galder Zamarreño (JIRA)

ModClusterListener not working with Embedded Tomcat 6 ----------------------------------------------------- Key: MODCLUSTER-187 URL: https://jira.jboss.org/browse/MODCLUSTER-187 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Final Reporter: Galder Zamarreño Assignee: Jean-Frederic Clere ModClusterListener does not work with embedded Tomcat. The listener does not seem to get called and hence it does not connect to mod_cluster httpd proxy. -- 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

12 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-201) update mod_cluster to use HTTP/1.1

by Samuel Mendenhall (JIRA)

update mod_cluster to use HTTP/1.1 ---------------------------------- Key: MODCLUSTER-201 URL: https://issues.jboss.org/browse/MODCLUSTER-201 Project: mod_cluster Issue Type: Feature Request Reporter: Samuel Mendenhall Assignee: Jean-Frederic Clere Priority: Minor Certain technologies like siteminder require the host header which is not present in HTTP/1.0 so siteminder won't work out of the box with HTTP/1.0 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
4
0 / 0

[JBoss JIRA] (MODCLUSTER-282) Add JGRoups support

by Jean-Frederic Clere (JIRA)

Jean-Frederic Clere created MODCLUSTER-282: ---------------------------------------------- Summary: Add JGRoups support Key: MODCLUSTER-282 URL: https://issues.jboss.org/browse/MODCLUSTER-282 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.2.0.Final Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 1.2.1.Beta1 https://community.jboss.org/wiki/MOD-CLUSTERDiscoveryProtocol -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-192) Add SSL stuff in the FAQ

by Jean-Frederic Clere (JIRA)

Add SSL stuff in the FAQ ------------------------ Key: MODCLUSTER-192 URL: https://jira.jboss.org/browse/MODCLUSTER-192 Project: mod_cluster Issue Type: Feature Request Environment: docs Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere we need something like: openssl pkcs12 -export -nokeys -in /home/jfclere/CA/cacert.pem -out ca.p12 because nothing explains how the ca.p12 is created. -- 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

12 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-191) JBoss Enterprise Application Platform * JBPAPP-5315 mod_cluster: proxy: dialog to 127.0.0.1:8009 (127.0.0.1) failed

by Jean-Frederic Clere (JIRA)

JBoss Enterprise Application Platform * JBPAPP-5315 mod_cluster: proxy: dialog to 127.0.0.1:8009 (127.0.0.1) failed -------------------------------------------------------------------------------------------------------------------------- Key: MODCLUSTER-191 URL: https://jira.jboss.org/browse/MODCLUSTER-191 Project: mod_cluster Issue Type: Bug Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere The problem is the following: +++ [Wed Oct 27 11:33:30 2010] [error] ajp_cping_cpong: apr_socket_recv failed [Wed Oct 27 11:33:30 2010] [debug] mod_proxy_cluster.c(1213): ajp_cping_cpong: Done [Wed Oct 27 11:33:30 2010] [debug] proxy_util.c(2029): proxy: ajp: has released connection for (127.0.0.1) +++ and later: +++ [Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(265): proxy: APR_BUCKET_IS_EOS [Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(270): proxy: data to read (max 8186 at 4) [Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(285): proxy: got 0 bytes of data [Wed Oct 27 11:33:55 2010] [debug] ajp_header.c(687): ajp_read_header: ajp_ilink_received 09 [Wed Oct 27 11:33:55 2010] [debug] ajp_header.c(697): ajp_parse_type: got 09 [Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(543): proxy: Processing of request failed backend: 1, output: 0 [Wed Oct 27 11:33:55 2010] [error] proxy: dialog to 127.0.0.1:8009 (127.0.0.1) failed +++ And the node is marked broken for a while, until: +++ Wed Oct 27 11:35:00 2010] [debug] proxy_util.c(1955): proxy: ajp: worker for (127.0.0.1) has been marked for retry +++ The STATUS should be able to restore the node and may be the answer 09 should not be taken as broken node error: it is just a broken socket 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

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] (MODCLUSTER-283) Refactor ModClusterConfig to allow complex types

by Paul Ferraro (JIRA)

Paul Ferraro created MODCLUSTER-283: --------------------------------------- Summary: Refactor ModClusterConfig to allow complex types Key: MODCLUSTER-283 URL: https://issues.jboss.org/browse/MODCLUSTER-283 Project: mod_cluster Issue Type: Enhancement Affects Versions: 1.2.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 1.2.1.Beta1 mod_cluster's configuration interfaces were originally designed to accept simple configuration property values. With AS7, complex property types (e.g. InetAddress, Collection<InetSocketAddress>, Set<String>) are easier to define - and the old methods are now cumbersome. We should keep the old mutator methods (for backwards compatibility), but alter the accessor methods to accept more complex types. e.g. Collection<InetSocketAddress> MCMPConfiguration.getProxies(); void ModClusterConfig.setProxies(Collection<InetSocketAddress>); void ModClusterConfig.setProxyList(String proxyList); InetAddress AdvertiseConfiguration.getAdvertiseGroupAddress(); void ModClusterConfig.setProxies(Collection<InetSocketAddress>); void ModClusterConfig.setProxyList(String proxyList); etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-211) SE Linux in RHEL 6 does not support mod_cluster in the context of HTTPD

by Jim Tyrrell (JIRA)

SE Linux in RHEL 6 does not support mod_cluster in the context of HTTPD ----------------------------------------------------------------------- Key: MODCLUSTER-211 URL: https://issues.jboss.org/browse/MODCLUSTER-211 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.0.4.GA Environment: Apache 2.2.15 in RHEL 6 with mod_cluster in EAP Reporter: Jim Tyrrell Assignee: Jean-Frederic Clere When trying to run mod_cluster module inside of Apache I need to create a custom SE Linux policy. This should not need to be done as RHEL should ship the correctly enabled SE Linux policy, although in talking with my resident RHEL expert, the error messaging is that mod_cluster is using write instead of append as the existing policy does. I will cross post this in BZ for the SE Linux team, as I am not sure where changes need to be made, I will update this ticket with that ticket number. The create SE Linux TE file looks like this: module jbosshttpd 1.0; require { type httpd_log_t; type httpd_t; type port_t; type soundd_port_t; class tcp_socket name_bind; class file write; class dir remove_name; class udp_socket name_bind; } #============= httpd_t ============== allow httpd_t httpd_log_t:dir remove_name; allow httpd_t httpd_log_t:file write; #!!!! This avc can be allowed using the boolean 'allow_ypbind' allow httpd_t port_t:udp_socket name_bind; allow httpd_t soundd_port_t:tcp_socket name_bind; -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
22
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-235) Support hot-standby worker nodes

by Samuel Mendenhall (JIRA)

Support hot-standby worker nodes -------------------------------- Key: MODCLUSTER-235 URL: https://issues.jboss.org/browse/MODCLUSTER-235 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.2.Final Reporter: Samuel Mendenhall Assignee: Jean-Frederic Clere Fix For: 1.1.3.Final Like in mod_proxy and mod_jk, mod_cluster should support the ability to keep a worker node in hot-standby. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
9
0 / 0

[JBoss JIRA] (MODCLUSTER-280) New node registering with mod_cluster makes server unresponsive

by Radoslav Husar (JIRA)

Radoslav Husar created MODCLUSTER-280: ----------------------------------------- Summary: New node registering with mod_cluster makes server unresponsive Key: MODCLUSTER-280 URL: https://issues.jboss.org/browse/MODCLUSTER-280 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.0.Beta4 Environment: Fedora 15 Reporter: Radoslav Husar Assignee: Jean-Frederic Clere Fix For: 1.2.0.Beta5 Scenario as in MODCLUSTER-279 and another node is starting, upon registration server doesn't response for 15 seconds -- see time difference. {noformat} Requesting http://127.0.0.1/load-demo/record @ Sun Jan 29 14:37:50 IST 2012 HTTP/1.1 200 OK Requesting http://127.0.0.1/load-demo/record @ Sun Jan 29 14:37:50 IST 2012 HTTP/1.1 200 OK Requesting http://127.0.0.1/load-demo/record @ Sun Jan 29 14:38:05 IST 2012 HTTP/1.1 200 OK Requesting http://127.0.0.1/load-demo/record @ Sun Jan 29 14:38:05 IST 2012 HTTP/1.1 200 OK {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues February 2012