October 2011 - mod_cluster-issues

[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, 6 months

4
4
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, 6 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, 6 months

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

3
9
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-194) When encrypting the mod_cluster traffic, can't use the http connector

by Samuel Mendenhall (JIRA)

When encrypting the mod_cluster traffic, can't use the http connector --------------------------------------------------------------------- Key: MODCLUSTER-194 URL: https://jira.jboss.org/browse/MODCLUSTER-194 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.0.Final Reporter: Samuel Mendenhall Assignee: Jean-Frederic Clere Priority: Minor It would appear not possible to use the http connector when encrypting the mod_cluster connection. For mod_cluster to use the 8443 connector in JBoss, one has to comment out both the 8009 connector and 8080. But this raises a question, even if it were possible to keep the 8080 connector, it doesn't appear mod_cluster is able to hit both, as there would need to be multiple mod_cluster VHs in httpd. -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-208) ClassCastException on updateClusterStatus()

by Bela Ban (JIRA)

ClassCastException on updateClusterStatus() ------------------------------------------- Key: MODCLUSTER-208 URL: https://issues.jboss.org/browse/MODCLUSTER-208 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Final Environment: JBoss AS 6.0.0.final Reporter: Bela Ban Assignee: Jean-Frederic Clere 13:55:36,731 ERROR [org.apache.catalina.core.ContainerBase] Exception invoking periodic operation: : java.lang.ClassCastException: org.jboss.modcluster.ha.rpc.DefaultRpcResponse cannot be cast to org.jboss.modcluster.ha.rpc.RpcResponse at org.jboss.modcluster.ha.HAModClusterService$ClusteredModClusterService.updateClusterStatus(HAModClusterService.java:1222) [:1.1.0.Final] at org.jboss.modcluster.ha.HAModClusterService$ClusteredModClusterService.status(HAModClusterService.java:1167) [:1.1.0.Final] at org.jboss.modcluster.ha.HAModClusterService.status(HAModClusterService.java:359) [:1.1.0.Final] at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:314) [:1.1.0.Final] at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [:6.0.0.Final] at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1335) [:6.0.0.Final] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1599) [:6.0.0.Final] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1588) [:6.0.0.Final] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
11
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-227) mod_proxy code for old httpd versions needs to be updated.

by Jean-Frederic Clere (JIRA)

mod_proxy code for old httpd versions needs to be updated. ---------------------------------------------------------- Key: MODCLUSTER-227 URL: https://issues.jboss.org/browse/MODCLUSTER-227 Project: mod_cluster Issue Type: Bug Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere the code is old (pre 2.2.15). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-248) Missing Documentation For mod_cluster with JBoss AS5

by Stefan Negrea (JIRA)

Missing Documentation For mod_cluster with JBoss AS5 ---------------------------------------------------- Key: MODCLUSTER-248 URL: https://issues.jboss.org/browse/MODCLUSTER-248 Project: mod_cluster Issue Type: Bug Reporter: Stefan Negrea Assignee: Jean-Frederic Clere On the current mod_cluster website there is no documentation on installing mod_cluster on a JBoss AS5 server. The documentation says that mod_cluster is distributed with the server and implies there is no additional configuration required. However, it does not include details like adding Listeners to <Server> tag and configuring the JMX MBean and dependencies. The documentation from the mod_cluster module delivered with the JBoss AS5 points to a website that is no longer valid (http://www.jboss.org/mod_cluster/java/config.html) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-256) mod_cluster management console/Status does not show exact mod_cluster version

by Radoslav Husar (JIRA)

mod_cluster management console/Status does not show exact mod_cluster version ----------------------------------------------------------------------------- Key: MODCLUSTER-256 URL: https://issues.jboss.org/browse/MODCLUSTER-256 Project: mod_cluster Issue Type: Bug Reporter: Radoslav Husar Assignee: Jean-Frederic Clere It is standard to show the version of the Apache mod, just like mod_jk status page shows. The status page says: {code} mod_cluster/1.1.x Auto Refresh show DUMP output show INFO output ... {code} I think the motivation was to show the MCMP protocol generation/version, however ideally the whole version should be printed out, to make live easier for customers and GSS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues October 2011