September 2011 - mod_cluster-issues

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

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

2
2
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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-243) mod_cluster throws warnings at shutdown in AS7

by Jean-Frederic Clere (JIRA)

mod_cluster throws warnings at shutdown in AS7 ---------------------------------------------- Key: MODCLUSTER-243 URL: https://issues.jboss.org/browse/MODCLUSTER-243 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.2.Final Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Priority: Minor Fix For: 1.1.3.Final At shutdown you get an warning: +++ 21:37:37,537 WARN [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-1) Failed to interrupt socket reception: java.io.IOException: Invalid argument at java.net.PlainDatagramSocketImpl.send(Native Method) [:1.6.0_22] at java.net.DatagramSocket.send(DatagramSocket.java:629) [:1.6.0_22] at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.interruptDatagramReader(AdvertiseListenerImpl.java:240) at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.stop(AdvertiseListenerImpl.java:262) at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.destroy(AdvertiseListenerImpl.java:278) at org.jboss.modcluster.ModClusterService.shutdown(ModClusterService.java:214) at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.destroy(CatalinaEventHandlerAdapter.java:374) at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.stop(CatalinaEventHandlerAdapter.java:144) at org.jboss.as.modcluster.ModClusterService.stop(ModClusterService.java:236) at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1819) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2302) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] +++ In fact that should be a debug... And the fix should go in mod_cluster. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-219) AS7 schema requires properties.

by Jean-Frederic Clere (JIRA)

AS7 schema requires properties. ------------------------------- Key: MODCLUSTER-219 URL: https://issues.jboss.org/browse/MODCLUSTER-219 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.1.Final Reporter: Jean-Frederic Clere Assignee: Paul Ferraro Fix For: 1.1.2.Final In the xsd we have: +++ <xs:complexType name="common-load-metricType" abstract="true"> <xs:sequence> <xs:element name="property" type="tns:propertyType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="weight" type="xs:int"/> <xs:attribute name="capacity" type="xs:double"/> </xs:complexType> +++ So a getProperties() and a setProperties() should be added AbstractLoadMetric for example? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-209) mod_cluster_manager need better presentation

by Anders Welen (JIRA)

mod_cluster_manager need better presentation -------------------------------------------- Key: MODCLUSTER-209 URL: https://issues.jboss.org/browse/MODCLUSTER-209 Project: mod_cluster Issue Type: Enhancement Affects Versions: 1.1.1.Final Reporter: Anders Welen Assignee: Jean-Frederic Clere Priority: Minor The mod_cluster_manager "show INFO output" status page has the following problems: 1. "Transferred" misspelled 2. Context is missing the number of requests PS. Why not make it easier to parse? look at mod_jk that support both properties and XML DS. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Commented: (MODCLUSTER-254) AS7-1718 CLONE - mod_cluster needs consistent naming

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-254?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-254: ------------------------------------------- So it looks like we can stick with the 2 -- mod_cluster and modcluster and solve all the problems. > AS7-1718 CLONE - mod_cluster needs consistent naming > ---------------------------------------------------- > > Key: MODCLUSTER-254 > URL: https://issues.jboss.org/browse/MODCLUSTER-254 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.1.3.Final > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Priority: Critical > > Cloning over from AS7-1718 to reflect the community upstream request in mod_cluster. > --- > We have been running into issues with misspelt modcluster, mod_cluster and mod-cluster (and Mod-cluster) for quite some time now, making difficult time for users. Surely there are sometimes rules where we can't stick to proper naming but we should then be able to minimize to two names. > *project name = mod_cluster > *console name = "Mod_cluster Status" > *xsd schema filename = mod-cluster (./docs/schema/jboss-as-mod-cluster_1_0.xsd) > *xmlns = modcluster (eg xmlns="urn:jboss:domain:modcluster:1.0") > *xs elements = mod-cluster (eg mod-cluster-config) > *schema comments = mod_cluster (eg <!-- mod_cluster parameters ...) > *jar name = mod_cluster (ie mod_cluster-1.1.3.Final) > I am not going to name the EAP5 components where names are significantly changed too. > We need this madness to stop soon enough ;-( -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (MODCLUSTER-255) mod_cluster MCMP should internally use "lbgroup" instead of "domain"

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-255?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-255: -------------------------------------- Assignee: Jean-Frederic Clere (was: Paul Ferraro) Description: Here is a requst to internally change MCPM to use lbgroup instead of domain but keep domain for compatibility reasons and a possible upgrade path. ------------------- AS7-1721 We removed the notion of "domain" in context of mod_cluster since 1.1.x in order not to be confused with notion of domains used in AS7 for management perspective. Currently, the XSD does not list out the LBGroup property but the CommonAttributes.java implementation parses the XML for "domain". {code} String DOMAIN = "domain"; {code} was: We removed the notion of "domain" in context of mod_cluster since 1.1.x in order not to be confused with notion of domains used in AS7 for management perspective. Currently, the XSD does not list out the LBGroup property but the CommonAttributes.java implementation parses the XML for "domain". {code} String DOMAIN = "domain"; {code} > mod_cluster MCMP should internally use "lbgroup" instead of "domain" > --------------------------------------------------------------------- > > Key: MODCLUSTER-255 > URL: https://issues.jboss.org/browse/MODCLUSTER-255 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.1.3.Final > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > > Here is a requst to internally change MCPM to use lbgroup instead of domain but keep domain for compatibility reasons and a possible upgrade path. > ------------------- > AS7-1721 > We removed the notion of "domain" in context of mod_cluster since 1.1.x in order not to be confused with notion of domains used in AS7 for management perspective. > Currently, the XSD does not list out the LBGroup property but the CommonAttributes.java implementation parses the XML for "domain". > {code} > String DOMAIN = "domain"; > {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Moved: (MODCLUSTER-255) mod_cluster MCMP should internally use "lbgroup" instead of "domain"

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-255?page=com.atlassian.jira.pl... ] Radoslav Husar moved AS7-1732 to MODCLUSTER-255: ------------------------------------------------ Project: mod_cluster (was: Application Server 7) Key: MODCLUSTER-255 (was: AS7-1732) Issue Type: Feature Request (was: Bug) Workflow: jira (was: GIT Pull Request workflow ) Affects Version/s: 1.1.3.Final (was: 7.0.0.Final) (was: 7.0.1.Final) Component/s: (was: Clustering) > mod_cluster MCMP should internally use "lbgroup" instead of "domain" > --------------------------------------------------------------------- > > Key: MODCLUSTER-255 > URL: https://issues.jboss.org/browse/MODCLUSTER-255 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.1.3.Final > Reporter: Radoslav Husar > Assignee: Paul Ferraro > > We removed the notion of "domain" in context of mod_cluster since 1.1.x in order not to be confused with notion of domains used in AS7 for management perspective. > Currently, the XSD does not list out the LBGroup property but the CommonAttributes.java implementation parses the XML for "domain". > {code} > String DOMAIN = "domain"; > {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Issue Comment Edited: (MODCLUSTER-254) AS7-1718 CLONE - mod_cluster needs consistent naming

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-254?page=com.atlassian.jira.pl... ] Jean-Frederic Clere edited comment on MODCLUSTER-254 at 9/5/11 10:07 AM: ------------------------------------------------------------------------- mod_cluster : C module + project name (that is why there is mod_cluster*.jar). modcluster: AS7 subsystem mod-cluster : prefix or suffix for the AS7 operations or attributes. was (Author: jfclere): mod_cluster : C module + project name (that is why it mod_cluster*.jar). modcluster: AS7 subsystem mod-cluster : prefix or suffix for the AS7 operations or attributes. > AS7-1718 CLONE - mod_cluster needs consistent naming > ---------------------------------------------------- > > Key: MODCLUSTER-254 > URL: https://issues.jboss.org/browse/MODCLUSTER-254 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.1.3.Final > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Priority: Critical > > Cloning over from AS7-1718 to reflect the community upstream request in mod_cluster. > --- > We have been running into issues with misspelt modcluster, mod_cluster and mod-cluster (and Mod-cluster) for quite some time now, making difficult time for users. Surely there are sometimes rules where we can't stick to proper naming but we should then be able to minimize to two names. > *project name = mod_cluster > *console name = "Mod_cluster Status" > *xsd schema filename = mod-cluster (./docs/schema/jboss-as-mod-cluster_1_0.xsd) > *xmlns = modcluster (eg xmlns="urn:jboss:domain:modcluster:1.0") > *xs elements = mod-cluster (eg mod-cluster-config) > *schema comments = mod_cluster (eg <!-- mod_cluster parameters ...) > *jar name = mod_cluster (ie mod_cluster-1.1.3.Final) > I am not going to name the EAP5 components where names are significantly changed too. > We need this madness to stop soon enough ;-( -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues September 2011