August 2017 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-439) Installation for Tomcat 6/7/8 is cumbersome: revamp distribution profile

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-439?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-439: -------------------------------------- Labels: tomcat ux (was: tomcat) > Installation for Tomcat 6/7/8 is cumbersome: revamp distribution profile > ------------------------------------------------------------------------ > > Key: MODCLUSTER-439 > URL: https://issues.jboss.org/browse/MODCLUSTER-439 > Project: mod_cluster > Issue Type: Task > Components: Documentation & Demos > Affects Versions: 1.2.0.Final, 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Labels: tomcat, ux > Fix For: 2.0.0.Alpha1, 1.4.0.Alpha1 > > > The installation in the docs now expects to go around and copy lots of jars to the /lib dir, the package we ship has all the tomcat 6 and 7 jars in the same spot... we shoud align this to be easier and/or include a readme file in the directory. Also update the documentation for people bulding from source. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-439) Installation for Tomcat 6/7/8 is cumbersome: revamp distribution profile

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-439?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-439: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Installation for Tomcat 6/7/8 is cumbersome: revamp distribution profile > ------------------------------------------------------------------------ > > Key: MODCLUSTER-439 > URL: https://issues.jboss.org/browse/MODCLUSTER-439 > Project: mod_cluster > Issue Type: Task > Components: Documentation & Demos > Affects Versions: 1.2.0.Final, 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Labels: tomcat, ux > Fix For: 2.0.0.Alpha1, 1.4.0.Alpha1 > > > The installation in the docs now expects to go around and copy lots of jars to the /lib dir, the package we ship has all the tomcat 6 and 7 jars in the same spot... we shoud align this to be easier and/or include a readme file in the directory. Also update the documentation for people bulding from source. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-439) Installation for Tomcat 6/7/8 is cumbersome: revamp distribution profile

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-439?page=com.atlassian.jira.pl... ] Work on MODCLUSTER-439 started by Radoslav Husar. ------------------------------------------------- > Installation for Tomcat 6/7/8 is cumbersome: revamp distribution profile > ------------------------------------------------------------------------ > > Key: MODCLUSTER-439 > URL: https://issues.jboss.org/browse/MODCLUSTER-439 > Project: mod_cluster > Issue Type: Task > Components: Documentation & Demos > Affects Versions: 1.2.0.Final, 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Labels: tomcat > Fix For: 2.0.0.Alpha1 > > > The installation in the docs now expects to go around and copy lots of jars to the /lib dir, the package we ship has all the tomcat 6 and 7 jars in the same spot... we shoud align this to be easier and/or include a readme file in the directory. Also update the documentation for people bulding from source. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-531) Eliminate automagic

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-531?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-531: -------------------------------------- Fix Version/s: 2.0.0.Alpha1 > Eliminate automagic > ------------------- > > Key: MODCLUSTER-531 > URL: https://issues.jboss.org/browse/MODCLUSTER-531 > Project: mod_cluster > Issue Type: Enhancement > Components: Core & Container Integration (Java), Documentation & Demos, Native (httpd modules) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > I am proposing we abandon automagic as much as possible. > h1. Problem > The main idea for automagic is to make deployment simple and easy to migrate/transfer and provide great user experience out of box. Unfortunately, this IMHO often backfires quite significantly resulting in configurations that are: > # insecure (listening on all interfaces, allow from all, default security key "changeme!") > # difficult to debug (not clear what is the actual configuration) > # unstable installations (seemingly unrelated aspects like adding an interface or connector break the config) > h1. Areas > There are several areas where automagic happens. > h5. Advertised address of the proxy > There were multiple bugs in the past, where 0.0.0.0 would be sent in the advertise mesages, now if its not explcit in the VirtualHost or passed in to ServerAdvertise, it automagically picks a non-local interface. Such configurations should be disallowed. > h5. Advertise interfaces > The interfaces are not explicit and advertise messages could be sent/received on more interfaces (related MODCLUSTER-487). This is also problematic when trying to move to DatagramChannel interface, which requires interfaces to be defined explicitly (MODCLUSTER-502). We can require this explicitly. > h5. Connector address > If bound to any-address, the address is inferred from the proxy connection as the local address. This is solved in the default WildFly configuration as its explicitly bound to a interface. > h5. Connector selection > This is solved in WildFly where selection is explicit. In tomcat this causes problems like MODCLUSTER-457 when WS requires http yet ajp is automatically selected by default. We can make this explicit. > h5. Route generation > Remove setJvmRoute from the SPI. -- 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 register with the proxy

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-457?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-457: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Expose Tomcat configuration to explicitly specify a connector to register 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 > Fix For: 2.0.0.Alpha1, 1.4.0.Alpha1 > > > 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 register with the proxy

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-457?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-457: -------------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/279 > Expose Tomcat configuration to explicitly specify a connector to register 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 > Fix For: 2.0.0.Alpha1 > > > 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 register with the proxy

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-457?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-457: -------------------------------------- Fix Version/s: 2.0.0.Alpha1 > Expose Tomcat configuration to explicitly specify a connector to register 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 > Fix For: 2.0.0.Alpha1 > > > 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-584) httpd Host header validation check with IPv6 address in MCMP requests

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-584?page=com.atlassian.jira.pl... ] Michal Karm Babacek reassigned MODCLUSTER-584: ---------------------------------------------- Assignee: Matus Madzin (was: George Zaronikas) > httpd Host header validation check with IPv6 address in MCMP requests > --------------------------------------------------------------------- > > Key: MODCLUSTER-584 > URL: https://issues.jboss.org/browse/MODCLUSTER-584 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 2.0.0.Alpha1, 1.2.13.Final, 1.3.6.Final > Reporter: Bogdan Sikora > Assignee: Matus Madzin > Priority: Blocker > > This is a regression as 2.4.23-GA works. > Reproducer: > 1. Set up httpd mod_cluster balancer with Ipv6 address with advertisement on. > 2. Set up worker node (tested with EAP) > 3. Checks on console if they correctly connect > {color:red}Issue:{color} > Httpd log: > {noformat} > [Wed May 10 04:41:31.930288 2017] [core:debug] [pid 15638] vhost.c(796): [client 2620:52:0:105f:5054:ff:fe22:d46f:44474] AH02415: [strict] Invalid host name '2620:52:0:105f:5054:ff:fe22:d46f', problem near: :52:0: > [Wed May 10 04:41:31.930332 2017] [core:debug] [pid 15638] vhost.c(891): [client 2620:52:0:105f:5054:ff:fe22:d46f:44474] AH00550: Client sent malformed Host header: 2620:52:0:105f:5054:ff:fe22:d46f:8747 > [Wed May 10 04:41:31.930338 2017] [core:debug] [pid 15638] protocol.c(1385): [client 2620:52:0:105f:5054:ff:fe22:d46f:44474] AH00569: client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): / > {noformat} > EAP6(6.4.10) log: > {noformat} > 04:41:29,316 ERROR [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000042: Error null sending INFO command to 2620:52:0:105f:5054:ff:fe22:d46f/2620:52:0:105f:5054:ff:fe22:d46f:8747, configuration will be reset: null > {noformat} > Tomcat log: > {noformat} > May 10, 2017 9:05:25 AM org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler sendRequest > ERROR: MODCLUSTER000042: Error null sending INFO command to 2620:52:0:105f:5054:ff:fe22:d46f/2620:52:0:105f:5054:ff:fe22:d46f:8747, configuration will be reset: null > {noformat} > Issue was reproduced with EAP-7.1.0.DR17 too. Httpd-2.4.23-GA don't have this issue. > Issue has some connection to ipv6 as some ipv6 tests passed. > Failed on: > 2620:52:0:105f:5054:ff:fe22:d46f, 2620:52:0:105f:5054:ff:fe0c:5717, 2620:52:0:105f:5054:ff:feb5:a642, ... > Passed on: > 2620:52:0:1040:e8f4:2bff:feef:e504, 2620:52:0:1040:440c:3ff:fee1:df02, ... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-584) httpd Host header validation check with IPv6 address in MCMP requests

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-584?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-584: ------------------------------------------- Tester: Jan Kašík (was: Bogdan Sikora) > httpd Host header validation check with IPv6 address in MCMP requests > --------------------------------------------------------------------- > > Key: MODCLUSTER-584 > URL: https://issues.jboss.org/browse/MODCLUSTER-584 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 2.0.0.Alpha1, 1.2.13.Final, 1.3.6.Final > Reporter: Bogdan Sikora > Assignee: Matus Madzin > Priority: Blocker > > This is a regression as 2.4.23-GA works. > Reproducer: > 1. Set up httpd mod_cluster balancer with Ipv6 address with advertisement on. > 2. Set up worker node (tested with EAP) > 3. Checks on console if they correctly connect > {color:red}Issue:{color} > Httpd log: > {noformat} > [Wed May 10 04:41:31.930288 2017] [core:debug] [pid 15638] vhost.c(796): [client 2620:52:0:105f:5054:ff:fe22:d46f:44474] AH02415: [strict] Invalid host name '2620:52:0:105f:5054:ff:fe22:d46f', problem near: :52:0: > [Wed May 10 04:41:31.930332 2017] [core:debug] [pid 15638] vhost.c(891): [client 2620:52:0:105f:5054:ff:fe22:d46f:44474] AH00550: Client sent malformed Host header: 2620:52:0:105f:5054:ff:fe22:d46f:8747 > [Wed May 10 04:41:31.930338 2017] [core:debug] [pid 15638] protocol.c(1385): [client 2620:52:0:105f:5054:ff:fe22:d46f:44474] AH00569: client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): / > {noformat} > EAP6(6.4.10) log: > {noformat} > 04:41:29,316 ERROR [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000042: Error null sending INFO command to 2620:52:0:105f:5054:ff:fe22:d46f/2620:52:0:105f:5054:ff:fe22:d46f:8747, configuration will be reset: null > {noformat} > Tomcat log: > {noformat} > May 10, 2017 9:05:25 AM org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler sendRequest > ERROR: MODCLUSTER000042: Error null sending INFO command to 2620:52:0:105f:5054:ff:fe22:d46f/2620:52:0:105f:5054:ff:fe22:d46f:8747, configuration will be reset: null > {noformat} > Issue was reproduced with EAP-7.1.0.DR17 too. Httpd-2.4.23-GA don't have this issue. > Issue has some connection to ipv6 as some ipv6 tests passed. > Failed on: > 2620:52:0:105f:5054:ff:fe22:d46f, 2620:52:0:105f:5054:ff:fe0c:5717, 2620:52:0:105f:5054:ff:feb5:a642, ... > Passed on: > 2620:52:0:1040:e8f4:2bff:feef:e504, 2620:52:0:1040:440c:3ff:fee1:df02, ... -- 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 register 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 register with the proxy (was: Expose Tomcat configuration to explicitly specify a connector to use with the proxy) > Expose Tomcat configuration to explicitly specify a connector to register 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues August 2017