April 2012 - mod_cluster-issues - Jboss List Archives

[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

1
1
0 / 0

[JBoss JIRA] (MODCLUSTER-296) Set X_FORWARDED_PROTO header when serving SSL

by Kevin Menard (JIRA)

Kevin Menard created MODCLUSTER-296: --------------------------------------- Summary: Set X_FORWARDED_PROTO header when serving SSL Key: MODCLUSTER-296 URL: https://issues.jboss.org/browse/MODCLUSTER-296 Project: mod_cluster Issue Type: Feature Request Reporter: Kevin Menard Assignee: Jean-Frederic Clere I'm using mod_cluster to connect my Torquebox server to Apache 2, serving up a Rails application. Since SSL termination is occurring at the Apache level, all communication between Apache and Torquebox (AS 7.1) is done without SSL. Rails then thinks it's working over plain HTTP and alters it's behavior accordingly: any generated URLs will use the "http" scheme and it will not allow the creation of cookies with the "secure" attribute set. I don't know if other frameworks behave similarly, but I suspect some do. As it turns out, setting the X_FORWARDED_PROTO header to "https" fixes the problem in Rails. It then knows that it's being served up over SSL. I've added it to my vhost, but it'd be nice if mod_cluster handled this out of the box. Unlike other proxy startegies, there's no clear way to tell mod_cluster to communicate over a secure channel to the AS instance. I think setting this header then is in keeping with the expected behavior. -- 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

2
2
0 / 0

[JBoss JIRA] (MODCLUSTER-298) mod_cluster doesn't work with IPv6

by Jean-Frederic Clere (JIRA)

Jean-Frederic Clere created MODCLUSTER-298: ---------------------------------------------- Summary: mod_cluster doesn't work with IPv6 Key: MODCLUSTER-298 URL: https://issues.jboss.org/browse/MODCLUSTER-298 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.1.Beta1, MOD_CLUSTER_1_0_10_GA_CP02 Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 1.2.1.Beta2 the node does code : format the way the native part expects it. the handing of : format is wrong for the cping/cpong logic. -- 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

2
10
0 / 0

[JBoss JIRA] (MODCLUSTER-302) Allow proxy connector to be specified explicitly (instead of dynamically selecting one)

by Paul Ferraro (JIRA)

Paul Ferraro created MODCLUSTER-302: --------------------------------------- Summary: Allow proxy connector to be specified explicitly (instead of dynamically selecting one) Key: MODCLUSTER-302 URL: https://issues.jboss.org/browse/MODCLUSTER-302 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.2.1.Beta1 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 1.2.1.Beta2 -- 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

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

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

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

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

3
7
0 / 0

[JBoss JIRA] (MODCLUSTER-285) get_path_param in mod_proxy_cluster doesn't expect '; ' as separator

by Stefano Nichele (JIRA)

Stefano Nichele created MODCLUSTER-285: ------------------------------------------ Summary: get_path_param in mod_proxy_cluster doesn't expect ';' as separator Key: MODCLUSTER-285 URL: https://issues.jboss.org/browse/MODCLUSTER-285 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.0.Final, 1.1.3.Final Reporter: Stefano Nichele Assignee: Jean-Frederic Clere Current version of get_path_param doesn't expect ';' as path parameters separator so this urls are not correctly handled: /test.jsp;jsessionid=123123.NODE01;name=vale See for instance the mod_proxy_balancer implementation (in httpd 2.2.21): /* Retrieve the parameter with the given name * Something like 'JSESSIONID=12345...N' */ static char *get_path_param(apr_pool_t *pool, char *url, const char *name, int scolon_sep) { char *path = NULL; char *pathdelims = "?&"; if (scolon_sep) { pathdelims = ";?&"; } for (path = strstr(url, name); path; path = strstr(path + 1, name)) { path += strlen(name); if (*path == '=') { /* * Session path was found, get it's value */ ++path; if (strlen(path)) { char *q; path = apr_strtok(apr_pstrdup(pool, path), pathdelims, &q); return path; } } } return NULL; } Severity of this bug to me is not so high since using more than one path parameters is not so common. -- 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

2
4
0 / 0

[JBoss JIRA] (MODCLUSTER-287) Demo load servlet needs to be rewritten to not rely on JMX.

by Paul Ferraro (JIRA)

Paul Ferraro created MODCLUSTER-287: --------------------------------------- Summary: Demo load servlet needs to be rewritten to not rely on JMX. Key: MODCLUSTER-287 URL: https://issues.jboss.org/browse/MODCLUSTER-287 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 1.2.1.Beta1 -- 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

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues April 2012