mod_cluster-issues August 2016

mod_cluster-issues@lists.jboss.org

1 participants
63 discussions

[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 commented on MODCLUSTER-457: ------------------------------------------- In WildFly our connectors are named, however in Tomcat connectors are not named (org.apache.catalina.connector.Connector) thus one more reason for auto-selection of the connector. We would need to differentiate by scheme (still does not uniquely identifies the connector) or port, which is not an elegant solution. Ideas [~jfclere], [~pferraro]? > 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: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.2.11.Final, 1.3.1.Final > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Fix For: 1.3.4.Final > > > 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 (v6.4.11#64026)

7 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: -------------------------------------- Workaround Description: Comment out / delete AJP connector configuration from server.xml (was: Delete AJP connector configuration from server.xml) > 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: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.2.11.Final, 1.3.1.Final > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Fix For: 1.3.4.Final > > > 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 (v6.4.11#64026)

7 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... ] Work on MODCLUSTER-457 started by Radoslav Husar. ------------------------------------------------- > 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: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.2.11.Final, 1.3.1.Final > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Fix For: 1.3.4.Final > > > 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 (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

← Newer
1
2
3
4
5
6
7
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues August 2016