June 2011 - mod_cluster-issues - Jboss List Archives

[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] 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, 2 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, 2 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-231) mod_cluster forgets removed node too fast

by Radoslav Husar (JIRA)

mod_cluster forgets removed node too fast ----------------------------------------- Key: MODCLUSTER-231 URL: https://issues.jboss.org/browse/MODCLUSTER-231 Project: mod_cluster Issue Type: Enhancement Affects Versions: 1.0.10 Reporter: Radoslav Husar Assignee: Jean-Frederic Clere Priority: Minor See JBPAPP-6326. WAITFORREMOVE should be configurable (as it is currently hardcoded to be 10 seconds). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-236) Allow context lengths greater than 40

by Samuel Mendenhall (JIRA)

Allow context lengths greater than 40 ------------------------------------- Key: MODCLUSTER-236 URL: https://issues.jboss.org/browse/MODCLUSTER-236 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 The mod_cluster 1.1 documentation states the following in the Limitation section: "Max context length 40 (for example myapp.war deploys in /myapp /myapp is the context)." This value should be at least doubled to 80 for use with ESB which creates long context names. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-105) Refactor mod_cluster to allow implementations for other application servers

by Paul Ferraro (JIRA)

Refactor mod_cluster to allow implementations for other application servers --------------------------------------------------------------------------- Key: MODCLUSTER-105 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-105 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.0.2.GA Reporter: Paul Ferraro Assignee: Paul Ferraro Split current jar into a -core.jar containing APIs, and isolate catalina implementation to a separate -catalina.jar. -- 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

12 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-112) Refactor project into modules for HA, catalina, core, etc.

by Paul Ferraro (JIRA)

Refactor project into modules for HA, catalina, core, etc. ---------------------------------------------------------- Key: MODCLUSTER-112 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-112 Project: mod_cluster Issue Type: Sub-task Reporter: Paul Ferraro Assignee: Jean-Frederic Clere Restructure maven project to create separate module jars. mod-cluster-spi: ContainerEventHandler, Server, Engine, Connector, Host, Context mod-cluster-core: ModClusterService and dependencies mod-cluster-ha: HAModClusterService and dependencies mod-cluster-catalina: ModClusterListener, CatalinaEventHandlerAdapter and spi implementation -- 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

12 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-151) Modify jbossweb metrics to use service provider spi, instead of jmx

by Paul Ferraro (JIRA)

Modify jbossweb metrics to use service provider spi, instead of jmx ------------------------------------------------------------------- Key: MODCLUSTER-151 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-151 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.0.CR1 Reporter: Paul Ferraro Assignee: Paul Ferraro Currently, the jbossweb load metrics (i.e. ActiveSessionsLoadMetric, BusyConnectorsLoadMetric, RequestCountLoadMetric, ReceiveTrafficLoadMetric, SendTrafficLoadMetric) use jmx to generate their load values. This is potentially fragile. Instead, these load metrics should use org.jboss.mod_cluster.Engine as a load context. This raises the issue of load value scope. Currently, load is scoped to a server. Really, this should be scoped to an engine. While server:engine is usually a 1:1 relationship, this is technically a 1:N relationship. Suggested API change: class LoadMetricSource<C extends LoadContext> { C createContext(Engine engine); } Where there exists: class EngineLoadMetricSource<EngineLoadContext> { public EngineLoadContext createContext(Engine engine) { return new EngineLoadContext(engine); } } class EngineLoadContext implements LoadContext { private final Engine engine; public EngineLoadContext(Engine engine) { this.engine = engine; } public Engine getEngine() { return this.engine; } public void close() { // Nothing to close } } The various jbossweb load metrics would use this source. -- 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

12 years, 4 months

6
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues June 2011