August 2017 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-457) Expose Tomcat configuration to explicitly specify a connector to use with the proxy

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-457?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-457: ------------------------------------------- Just to note, the problem from the field is that since the connectors are chosen automagically, people were forced to bump thread counts e.g. by 1, so that the connector with higher thread count is chosen. > Expose Tomcat configuration to explicitly specify a connector to use with the proxy > ----------------------------------------------------------------------------------- > > Key: MODCLUSTER-457 > URL: https://issues.jboss.org/browse/MODCLUSTER-457 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Affects Versions: 1.2.11.Final, 1.3.1.Final > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Priority: Blocker > Labels: ux > > Configuring mod_cluster to leverage {{ws://}} with {{EnableWsTunnel}} (mod_proxy_wstunnel) requires the Tomcat to use *http* instead of *ajp* connector. > Unlike [AS7/WildFly/EAP|https://github.com/wildfly/wildfly/blob/master/mod_cluste...] mod_cluster integration, the Tomcat one ignores such option, i.e. there is nothing about selecting a particular connector with a *connector* attribute in [mbeans-descriptors.xml|https://github.com/modcluster/mod_cluster/blob/b3a...]. > <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" > loadMetricClass="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric" > loadMetricCapacity="1" loadHistory="9" loadDecayFactor="2" stickySession="true" > stickySessionForce="false" stickySessionRemove="true" advertise="true" > {color:red}*connector="http"*{color} advertiseGroupAddress="224.0.5.12" advertisePort="61217" > /> > Suggestion: Let's add the option to the catalina integration as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-457) Expose Tomcat configuration to explicitly specify a connector to use with the proxy

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-457?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-457: -------------------------------------- Priority: Blocker (was: Critical) > Expose Tomcat configuration to explicitly specify a connector to use with the proxy > ----------------------------------------------------------------------------------- > > Key: MODCLUSTER-457 > URL: https://issues.jboss.org/browse/MODCLUSTER-457 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Affects Versions: 1.2.11.Final, 1.3.1.Final > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Priority: Blocker > Labels: ux > > Configuring mod_cluster to leverage {{ws://}} with {{EnableWsTunnel}} (mod_proxy_wstunnel) requires the Tomcat to use *http* instead of *ajp* connector. > Unlike [AS7/WildFly/EAP|https://github.com/wildfly/wildfly/blob/master/mod_cluste...] mod_cluster integration, the Tomcat one ignores such option, i.e. there is nothing about selecting a particular connector with a *connector* attribute in [mbeans-descriptors.xml|https://github.com/modcluster/mod_cluster/blob/b3a...]. > <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" > loadMetricClass="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric" > loadMetricCapacity="1" loadHistory="9" loadDecayFactor="2" stickySession="true" > stickySessionForce="false" stickySessionRemove="true" advertise="true" > {color:red}*connector="http"*{color} advertiseGroupAddress="224.0.5.12" advertisePort="61217" > /> > Suggestion: Let's add the option to the catalina integration as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-457) Expose Tomcat configuration to explicitly specify a connector to use with the proxy

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-457?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-457: -------------------------------------- Labels: ux (was: ) > Expose Tomcat configuration to explicitly specify a connector to use with the proxy > ----------------------------------------------------------------------------------- > > Key: MODCLUSTER-457 > URL: https://issues.jboss.org/browse/MODCLUSTER-457 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Affects Versions: 1.2.11.Final, 1.3.1.Final > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Priority: Blocker > Labels: ux > > Configuring mod_cluster to leverage {{ws://}} with {{EnableWsTunnel}} (mod_proxy_wstunnel) requires the Tomcat to use *http* instead of *ajp* connector. > Unlike [AS7/WildFly/EAP|https://github.com/wildfly/wildfly/blob/master/mod_cluste...] mod_cluster integration, the Tomcat one ignores such option, i.e. there is nothing about selecting a particular connector with a *connector* attribute in [mbeans-descriptors.xml|https://github.com/modcluster/mod_cluster/blob/b3a...]. > <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" > loadMetricClass="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric" > loadMetricCapacity="1" loadHistory="9" loadDecayFactor="2" stickySession="true" > stickySessionForce="false" stickySessionRemove="true" advertise="true" > {color:red}*connector="http"*{color} advertiseGroupAddress="224.0.5.12" advertisePort="61217" > /> > Suggestion: Let's add the option to the catalina integration as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-457) Tomcat mod_cluster integration does not allow one to choose a connector

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-457?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-457: -------------------------------------- Issue Type: Feature Request (was: Bug) > Tomcat mod_cluster integration does not allow one to choose a connector > ----------------------------------------------------------------------- > > Key: MODCLUSTER-457 > URL: https://issues.jboss.org/browse/MODCLUSTER-457 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Affects Versions: 1.2.11.Final, 1.3.1.Final > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Priority: Critical > > Configuring mod_cluster to leverage {{ws://}} with {{EnableWsTunnel}} (mod_proxy_wstunnel) requires the Tomcat to use *http* instead of *ajp* connector. > Unlike [AS7/WildFly/EAP|https://github.com/wildfly/wildfly/blob/master/mod_cluste...] mod_cluster integration, the Tomcat one ignores such option, i.e. there is nothing about selecting a particular connector with a *connector* attribute in [mbeans-descriptors.xml|https://github.com/modcluster/mod_cluster/blob/b3a...]. > <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" > loadMetricClass="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric" > loadMetricCapacity="1" loadHistory="9" loadDecayFactor="2" stickySession="true" > stickySessionForce="false" stickySessionRemove="true" advertise="true" > {color:red}*connector="http"*{color} advertiseGroupAddress="224.0.5.12" advertisePort="61217" > /> > Suggestion: Let's add the option to the catalina integration as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-457) Expose Tomcat configuration to explicitly specify a connector to use with the proxy

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-457?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-457: -------------------------------------- Summary: Expose Tomcat configuration to explicitly specify a connector to use with the proxy (was: Tomcat mod_cluster integration does not allow one to choose a connector) > Expose Tomcat configuration to explicitly specify a connector to use with the proxy > ----------------------------------------------------------------------------------- > > Key: MODCLUSTER-457 > URL: https://issues.jboss.org/browse/MODCLUSTER-457 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Affects Versions: 1.2.11.Final, 1.3.1.Final > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Priority: Critical > > Configuring mod_cluster to leverage {{ws://}} with {{EnableWsTunnel}} (mod_proxy_wstunnel) requires the Tomcat to use *http* instead of *ajp* connector. > Unlike [AS7/WildFly/EAP|https://github.com/wildfly/wildfly/blob/master/mod_cluste...] mod_cluster integration, the Tomcat one ignores such option, i.e. there is nothing about selecting a particular connector with a *connector* attribute in [mbeans-descriptors.xml|https://github.com/modcluster/mod_cluster/blob/b3a...]. > <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" > loadMetricClass="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric" > loadMetricCapacity="1" loadHistory="9" loadDecayFactor="2" stickySession="true" > stickySessionForce="false" stickySessionRemove="true" advertise="true" > {color:red}*connector="http"*{color} advertiseGroupAddress="224.0.5.12" advertisePort="61217" > /> > Suggestion: Let's add the option to the catalina integration as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-607) Support floating-point numerals for decay factor

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-607?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-607: -------------------------------------- Fix Version/s: 2.0.0.Alpha1 > Support floating-point numerals for decay factor > ------------------------------------------------ > > Key: MODCLUSTER-607 > URL: https://issues.jboss.org/browse/MODCLUSTER-607 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Affects Versions: 1.2.13.Final, 1.3.7.Final > Reporter: Leandro Quiroga > Assignee: Radoslav Husar > Labels: decay > Fix For: 2.0.0.Alpha1 > > > The int type is too restrictive for specifying the decay factor. > Using a decay factor of 1 means no decay. > Next value is 2, and the importance of loads decreases too fast: > ||Instant||Importance|| > |0|100%| > |1|50%| > |2|25%| > |3|12.5%| > |4|6.3%| > |5|3.1%| > |6|1.6%| > |7|0.8%| > |8|0.4%| > |9|0.2%| > Next value is 3, and the importance of loads decreases even faster: > ||Instant||Importance|| > |0|100%| > |1|33%| > |2|11%| > |3|3.7%| > |4|1.2%| > |5|0.4%| > |6|0.1%| > |7|0.0%| > |8|0.0%| > |9|0.0%| > > Using a double for decay factor isn't complex and allows much more precision. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-607) Support floating-point numerals for decay factor

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-607?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-607: -------------------------------------- Priority: Major (was: Minor) > Support floating-point numerals for decay factor > ------------------------------------------------ > > Key: MODCLUSTER-607 > URL: https://issues.jboss.org/browse/MODCLUSTER-607 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Affects Versions: 1.2.13.Final, 1.3.7.Final > Reporter: Leandro Quiroga > Assignee: Radoslav Husar > Labels: decay > Fix For: 2.0.0.Alpha1 > > > The int type is too restrictive for specifying the decay factor. > Using a decay factor of 1 means no decay. > Next value is 2, and the importance of loads decreases too fast: > ||Instant||Importance|| > |0|100%| > |1|50%| > |2|25%| > |3|12.5%| > |4|6.3%| > |5|3.1%| > |6|1.6%| > |7|0.8%| > |8|0.4%| > |9|0.2%| > Next value is 3, and the importance of loads decreases even faster: > ||Instant||Importance|| > |0|100%| > |1|33%| > |2|11%| > |3|3.7%| > |4|1.2%| > |5|0.4%| > |6|0.1%| > |7|0.0%| > |8|0.0%| > |9|0.0%| > > Using a double for decay factor isn't complex and allows much more precision. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-607) Support floating-point numerals for decay factor

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-607?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-607: -------------------------------------- Issue Type: Feature Request (was: Enhancement) > Support floating-point numerals for decay factor > ------------------------------------------------ > > Key: MODCLUSTER-607 > URL: https://issues.jboss.org/browse/MODCLUSTER-607 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Affects Versions: 1.2.13.Final, 1.3.7.Final > Reporter: Leandro Quiroga > Assignee: Radoslav Husar > Priority: Minor > Labels: decay > Fix For: 2.0.0.Alpha1 > > > The int type is too restrictive for specifying the decay factor. > Using a decay factor of 1 means no decay. > Next value is 2, and the importance of loads decreases too fast: > ||Instant||Importance|| > |0|100%| > |1|50%| > |2|25%| > |3|12.5%| > |4|6.3%| > |5|3.1%| > |6|1.6%| > |7|0.8%| > |8|0.4%| > |9|0.2%| > Next value is 3, and the importance of loads decreases even faster: > ||Instant||Importance|| > |0|100%| > |1|33%| > |2|11%| > |3|3.7%| > |4|1.2%| > |5|0.4%| > |6|0.1%| > |7|0.0%| > |8|0.0%| > |9|0.0%| > > Using a double for decay factor isn't complex and allows much more precision. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-607) Support floating-point numerals for decay factor

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-607?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-607: -------------------------------------- Summary: Support floating-point numerals for decay factor (was: Double decay factor) > Support floating-point numerals for decay factor > ------------------------------------------------ > > Key: MODCLUSTER-607 > URL: https://issues.jboss.org/browse/MODCLUSTER-607 > Project: mod_cluster > Issue Type: Enhancement > Components: Core & Container Integration (Java) > Affects Versions: 1.2.13.Final, 1.3.7.Final > Reporter: Leandro Quiroga > Assignee: Radoslav Husar > Priority: Minor > Labels: decay > Fix For: 2.0.0.Alpha1 > > > The int type is too restrictive for specifying the decay factor. > Using a decay factor of 1 means no decay. > Next value is 2, and the importance of loads decreases too fast: > ||Instant||Importance|| > |0|100%| > |1|50%| > |2|25%| > |3|12.5%| > |4|6.3%| > |5|3.1%| > |6|1.6%| > |7|0.8%| > |8|0.4%| > |9|0.2%| > Next value is 3, and the importance of loads decreases even faster: > ||Instant||Importance|| > |0|100%| > |1|33%| > |2|11%| > |3|3.7%| > |4|1.2%| > |5|0.4%| > |6|0.1%| > |7|0.0%| > |8|0.0%| > |9|0.0%| > > Using a double for decay factor isn't complex and allows much more precision. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-607) Double decay factor

by Leandro Quiroga (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-607?page=com.atlassian.jira.pl... ] Leandro Quiroga commented on MODCLUSTER-607: -------------------------------------------- Hi [~rhusar], I have made a pull request changing decay factor type from int to float. I think it is not necessary to use double, float is enough. > Double decay factor > ------------------- > > Key: MODCLUSTER-607 > URL: https://issues.jboss.org/browse/MODCLUSTER-607 > Project: mod_cluster > Issue Type: Enhancement > Components: Core & Container Integration (Java) > Affects Versions: 1.2.13.Final, 1.3.7.Final > Reporter: Leandro Quiroga > Assignee: Radoslav Husar > Priority: Minor > Labels: decay > > The int type is too restrictive for specifying the decay factor. > Using a decay factor of 1 means no decay. > Next value is 2, and the importance of loads decreases too fast: > ||Instant||Importance|| > |0|100%| > |1|50%| > |2|25%| > |3|12.5%| > |4|6.3%| > |5|3.1%| > |6|1.6%| > |7|0.8%| > |8|0.4%| > |9|0.2%| > Next value is 3, and the importance of loads decreases even faster: > ||Instant||Importance|| > |0|100%| > |1|33%| > |2|11%| > |3|3.7%| > |4|1.2%| > |5|0.4%| > |6|0.1%| > |7|0.0%| > |8|0.0%| > |9|0.0%| > > Using a double for decay factor isn't complex and allows much more precision. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 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 August 2017