May 2016 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-495) mod_cluster UDP multicast listener does not honour the proper interface

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-495?page=com.atlassian.jira.pl... ] Radoslav Husar reopened MODCLUSTER-495: --------------------------------------- > mod_cluster UDP multicast listener does not honour the proper interface > ----------------------------------------------------------------------- > > Key: MODCLUSTER-495 > URL: https://issues.jboss.org/browse/MODCLUSTER-495 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.1.Final > Environment: Linux, multiple NICs > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > > h3. Wrong interface > On a multi-interface systems, it is necessary to pick the right interface the balancer should send to > and worker should receive from. Merely setting UDP multicast address and port is not enough. > * With Apache HTTP Server, this is achieved by {{AdvertiseBindAddress}} directive (though the default is wrong MODCLUSTER-487) > * With Undertow mod_cluster proxy in Wildfly, the {{interface}} could be set in socket bindings, e.g.: {code}<socket-binding name="modcluster-adv" port="7637" multicast-address="224.0.1.105" multicast-port="7637" interface="special-public"/>{code} > * In the case of Tomcat/JBossWeb, [historical mod_cluster 1.x|http://docs.jboss.org/mod_cluster/1.1.0/html_single/#d0e1113] documentation suggests that it is done "automatically": _interface on which mod_cluster's internal connection was established_. > The statement from the historical documentation doesn't make much sense to me -- which internal connection? > The actual result is that if you have 2 boxes, 2 interfaces each: > h4. Balancer (Undertow or Apache HTTP Server) > {{Box 1: enp1s0:10.16.88.186, enp2s0:172.17.71.254}}, all connectors including advertisement bound to {{enp2s0:172.17.71.254}} > h4. Worker (Tomcat) > {{Box 2: enp1s0:10.16.88.181, enp2s0:172.17.66.254}}, HTTP/AJP connectors bound to {{enp2s0:172.17.66.254}} > {code} > <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" advertise="true" > loadMetricClass="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric" > loadMetricCapacity="1" loadHistory="9" loadDecayFactor="2" > stickySession="true" stickySessionForce="false" stickySessionRemove="true" > excludedContexts="ROOT,manager,docs,examples,host-manager" > autoEnableContexts="true" advertiseGroupAddress="224.0.1.105" advertisePort="7637" > <Connector address="172.17.66.254" port="8080" protocol="HTTP/1.1" > connectionTimeout="20000" > redirectPort="8443" /> > <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" address="172.17.66.254"/> > <Engine name="Catalina" defaultHost="localhost" jvmRoute="172.17.66.254node"> > {code} > The worker node *is unable to receive balancer's advertising*. The tomcat actually listens for advertisements on {{enp1s0:10.16.88.181}}, because if I rebind the balancer to {{enp1s0:10.16.88.186}}, the whole setup suddenly works. I also verified it with the Advertize.java utility. > h3. Suggestion > IMHO, we have to either make it configurable via listener's attribute or fetch the interface from one of the available connectors (sometimes AJP is not configured, sometimes HTTP(S) ain't -- but at least one is always present). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-496) Drop support for legacy JBoss AS versions (sar module)

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-496?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-496: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/176 > Drop support for legacy JBoss AS versions (sar module) > ------------------------------------------------------ > > Key: MODCLUSTER-496 > URL: https://issues.jboss.org/browse/MODCLUSTER-496 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-420) Move private API dependent code to a separate layer and drop old httpd

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-420?page=com.atlassian.jira.pl... ] Michal Karm Babacek commented on MODCLUSTER-420: ------------------------------------------------ This is a "Zero Ifdef initiative" - I'm about to add helpers that process formerly httpd dependant mod_proxy version API calls. The final state is having ifdefs limited to a single compatibility layer file. Source of wisdom: [Ben Klemens|http://ben.klemens.org/] > Move private API dependent code to a separate layer and drop old httpd > ---------------------------------------------------------------------- > > Key: MODCLUSTER-420 > URL: https://issues.jboss.org/browse/MODCLUSTER-420 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Michal Karm Babacek > Fix For: 2.0.0.Alpha1 > > > The EWS is built on 2.2.24 and further on when productizing modcluster, this version might even increase. Lets consider dropping older versions prior to this one. > If the decision is made, you can assign to me to remove the support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-420) Move private API dependent code to a separate layer and drop old httpd

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-420?page=com.atlassian.jira.pl... ] Work on MODCLUSTER-420 started by Michal Karm Babacek. ------------------------------------------------------ > Move private API dependent code to a separate layer and drop old httpd > ---------------------------------------------------------------------- > > Key: MODCLUSTER-420 > URL: https://issues.jboss.org/browse/MODCLUSTER-420 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Michal Karm Babacek > Fix For: 2.0.0.Alpha1 > > > The EWS is built on 2.2.24 and further on when productizing modcluster, this version might even increase. Lets consider dropping older versions prior to this one. > If the decision is made, you can assign to me to remove the support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-420) Move private API dependent code to a separate layer and drop old httpd

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-420?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-420: ------------------------------------------- Summary: Move private API dependent code to a separate layer and drop old httpd (was: Drop support for very old versions of httpd) > Move private API dependent code to a separate layer and drop old httpd > ---------------------------------------------------------------------- > > Key: MODCLUSTER-420 > URL: https://issues.jboss.org/browse/MODCLUSTER-420 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Michal Karm Babacek > Fix For: 2.0.0.Alpha1 > > > The EWS is built on 2.2.24 and further on when productizing modcluster, this version might even increase. Lets consider dropping older versions prior to this one. > If the decision is made, you can assign to me to remove the support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-420) Drop support for very old versions of httpd

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-420?page=com.atlassian.jira.pl... ] Michal Karm Babacek reassigned MODCLUSTER-420: ---------------------------------------------- Assignee: Michal Karm Babacek (was: Radoslav Husar) > Drop support for very old versions of httpd > ------------------------------------------- > > Key: MODCLUSTER-420 > URL: https://issues.jboss.org/browse/MODCLUSTER-420 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Michal Karm Babacek > Fix For: 2.0.0.Alpha1 > > > The EWS is built on 2.2.24 and further on when productizing modcluster, this version might even increase. Lets consider dropping older versions prior to this one. > If the decision is made, you can assign to me to remove the support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-496) Drop support for legacy JBoss AS versions (sar module)

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-496?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-496: -------------------------------------- Summary: Drop support for legacy JBoss AS versions (sar module) (was: Drop support for legacy JBoss AS 5.x (sar module)) > Drop support for legacy JBoss AS versions (sar module) > ------------------------------------------------------ > > Key: MODCLUSTER-496 > URL: https://issues.jboss.org/browse/MODCLUSTER-496 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-496) Drop support for legacy JBoss AS 5.x (sar module)

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-496?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-496: -------------------------------------- Summary: Drop support for legacy JBoss AS 5.x (sar module) (was: Drop support for legacy JBoss AS (sar module)) > Drop support for legacy JBoss AS 5.x (sar module) > ------------------------------------------------- > > Key: MODCLUSTER-496 > URL: https://issues.jboss.org/browse/MODCLUSTER-496 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-496) Drop support for legacy JBoss AS (sar module)

by Radoslav Husar (JIRA)

Radoslav Husar created MODCLUSTER-496: ----------------------------------------- Summary: Drop support for legacy JBoss AS (sar module) Key: MODCLUSTER-496 URL: https://issues.jboss.org/browse/MODCLUSTER-496 Project: mod_cluster Issue Type: Task Components: Core & Container Integration (Java) Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 2.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-420) Drop support for very old versions of httpd

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-420?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-420: -------------------------------------- Summary: Drop support for very old versions of httpd (was: Consider dropping support for very old versions of httpd) > Drop support for very old versions of httpd > ------------------------------------------- > > Key: MODCLUSTER-420 > URL: https://issues.jboss.org/browse/MODCLUSTER-420 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > The EWS is built on 2.2.24 and further on when productizing modcluster, this version might even increase. Lets consider dropping older versions prior to this one. > If the decision is made, you can assign to me to remove the support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues May 2016