March 2012 - mod_cluster-issues - Jboss List Archives

[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] (MODCLUSTER-297) Warnings when compiling mod_cluster

by Jean-Frederic Clere (JIRA)

Jean-Frederic Clere created MODCLUSTER-297: ---------------------------------------------- Summary: Warnings when compiling mod_cluster Key: MODCLUSTER-297 URL: https://issues.jboss.org/browse/MODCLUSTER-297 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.1.Beta1 Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Priority: Minor Fix For: 1.2.1.Beta2 Solaris gives the following warning at compile time "mod_advertise.c", line 683: warning: implicit function declaration: getpid "mod_advertise.c", line 798: warning: argument #5 is incompatible with prototype: prototype: pointer to const void : "/tmp/xbroot/ROOT/include/httpd/ap_provider.h", line 50 argument : pointer to function(pointer to struct request_rec {pointer to struct apr_pool_t {..} pool, pointer to struct conn_rec {..} connection, pointer to struct server_rec {..} server, pointer to struct request_rec {..} next, pointer to struct request_rec {..} prev, pointer to struct request_rec {..} main, pointer to char the_request, int assbackwards, int proxyreq, int header_only, pointer to char protocol, int proto_num, pointer to const char hostname, long request_time, pointer to const char status_line, int status, pointer to const char method, int method_number, long allowed, pointer to struct apr_array_header_t {..} allowed_xmethods, pointer to struct ap_method_list_t {..} allowed_methods, long sent_bodyct, long bytes_sent, long mtime, int chunked, pointer to const char range, long clength, long remaining, long read_length, int read_body, int read_chunked, unsigned int expecting_100, pointer to struct apr_table_t {..} headers_in, pointer to struct apr_table_t {..} headers_out, pointer to struct apr_table_t {..} err_headers_out, pointer to struct apr_table_t {..} subprocess_env, pointer to struct apr_table_t {..} notes, pointer to const char content_type, pointer to const char handler, pointer to const char content_encoding, pointer to struct apr_array_header_t {..} content_languages, pointer to char vlist_validator, pointer to char user, pointer to char ap_auth_type, int no_cache, int no_local_copy, pointer to char unparsed_uri, pointer to char uri, pointer to char filename, pointer to char canonical_filename, pointer to char path_info, pointer to char args, struct apr_finfo_t {..} finfo, struct apr_uri_t {..} parsed_uri, int used_path_info, pointer to struct ap_conf_vector_t {..} per_dir_config, pointer to struct ap_conf_vector_t {..} request_config, pointer to const struct htaccess_result {..} htaccess, pointer to struct ap_filter_t {..} output_filters, pointer to struct ap_filter_t {..} input_filters, pointer to struct ap_filter_t {..} proto_output_filters, pointer to struct ap_filter_t {..} proto_input_filters, int eos_sent}) returning void -- 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
2
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] (MODCLUSTER-295) default suggested port for ServerAdvertise needs to be changed to 7777 or some other unprotected port for Chrome support

by Simeon Pinder (JIRA)

Simeon Pinder created MODCLUSTER-295: ---------------------------------------- Summary: default suggested port for ServerAdvertise needs to be changed to 7777 or some other unprotected port for Chrome support Key: MODCLUSTER-295 URL: https://issues.jboss.org/browse/MODCLUSTER-295 Project: mod_cluster Issue Type: Enhancement Affects Versions: 1.2.0.Final Environment: Default Httpd server provided for Linux in 1.2.0.Final release but this would affect all platforms. Reporter: Simeon Pinder Assignee: Jean-Frederic Clere Priority: Minor If you setup mod_cluster and use the default configuration/ports used in httpd.conf of 6666 in your initial modcluster configuration, when attempting to browse http://(server ip):6666/mod_cluster_manager from a Chrome browser you get "The webpage is not available". Initially this feels like a 'File Not Found' exception indicating that the mod_cluster module may not actually be setup correctly. On closer investigation you'll see that the actual error is: Error 312 (net::ERR_UNSAFE_PORT): Unknown error. There's a workaround is to change the port to another port not marked as 'secured' or do what is described here but this is a hurdle to new users trying to test out their mod_cluster integration with Chrome: http://superuser.com/questions/188006/how-to-fix-err-unsafe-port-error-on... Firefox loads the same page fine. Either way if it complicates modcluster setup and testing and we can get around it by suggesting a different port(ex. 7777) I think this is preferable. If not we should at a minimum include this as a note in the installation and trouble shooting guide. -- 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
1
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-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, 8 months

2
2
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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues March 2012