July 2016 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-440) Release 1.3.x binaries to mod-cluster.jboss.org/downloads

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-440?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-440: -------------------------------------- Fix Version/s: 1.3.4.Final (was: 1.3.3.Final) > Release 1.3.x binaries to mod-cluster.jboss.org/downloads > --------------------------------------------------------- > > Key: MODCLUSTER-440 > URL: https://issues.jboss.org/browse/MODCLUSTER-440 > Project: mod_cluster > Issue Type: Task > Components: Documentation & Demos > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > Fix For: 1.3.4.Final > > > We should really do this and at least we should release the JARs so people get Tomcat 8 support. People using AS7 or WildFly get their modcluster jars out of box. > ..and blog/tweet about it :-) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-448) mod_cluster crashes apache thread if multiple nodes report the same AJP connect string

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-448?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-448: -------------------------------------- Fix Version/s: 1.3.4.Final (was: 1.3.3.Final) > mod_cluster crashes apache thread if multiple nodes report the same AJP connect string > -------------------------------------------------------------------------------------- > > Key: MODCLUSTER-448 > URL: https://issues.jboss.org/browse/MODCLUSTER-448 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Affects Versions: 1.2.6.Final > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > Fix For: 1.2.14.Final, 1.3.4.Final > > > Reported on behalf of [Toby Murray|https://github.com/ToeBee]: > Tracking issue #[138|https://github.com/modcluster/mod_cluster/issues/138] > Let's carry on with any discussion here, on JIRA... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-449) Implement ramp-up when starting new nodes

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-449?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-449: -------------------------------------- Fix Version/s: 1.3.4.Final (was: 1.3.3.Final) > Implement ramp-up when starting new nodes > ----------------------------------------- > > Key: MODCLUSTER-449 > URL: https://issues.jboss.org/browse/MODCLUSTER-449 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 1.3.4.Final > > > IIUC this has been a problem since inception. The problem is that the initial load stays in effect for performing load-balancing decisions until a new stat interval kicks in. > This effect is mitigated by load decay over time, but for the time a new node joins in, it can get overloaded upon startup. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-450) Reenable testMulticastSocketNoCrossTalk test

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-450?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-450: -------------------------------------- Fix Version/s: 1.3.4.Final (was: 1.3.3.Final) > Reenable testMulticastSocketNoCrossTalk test > -------------------------------------------- > > Key: MODCLUSTER-450 > URL: https://issues.jboss.org/browse/MODCLUSTER-450 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.3.1.Beta2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.4.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-452) mod_cluster with WildFly reports 0.0.0.0 to the balancer

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-452?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-452: -------------------------------------- Fix Version/s: 1.3.4.Final (was: 1.3.3.Final) > mod_cluster with WildFly reports 0.0.0.0 to the balancer > -------------------------------------------------------- > > Key: MODCLUSTER-452 > URL: https://issues.jboss.org/browse/MODCLUSTER-452 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.0.Final > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Fix For: 1.3.4.Final > > > While I was working on [issue 138|https://github.com/modcluster/mod_cluster/issues/138] (MODCLUSTER-448), it came to my attention that one can't force EAP 6.4 Beta (jbossweb, mod_cluster 1.2.11) to send anything like {{ajp://0.0.0.0:8009}} to the balancer. If one sets the application server to bind to 0.0.0.0, mod_cluster core correctly guesses 127.0.0.1 and sends {{ajp://127.0.0.1:8009}} to the balancer. > On the contrary, WildFly goes only half way: it reports 127.0.0.1 in the log: > {noformat} > [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000012: default-server connector will use /127.0.0.1 > {noformat} > and yet it sends 0.0.0.0 to the balancer: > {noformat} > Node localhost (ajp://0.0.0.0:8009): > {noformat} > Note the {{localhost}} string in place of properly generated UUID: MODCLUSTER-451. > For some historical context, I suggest: MODCLUSTER-91 and MODCLUSTER-168 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 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: -------------------------------------- Fix Version/s: 1.3.4.Final (was: 1.3.3.Final) > 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: Jean-Frederic Clere > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-460) Silence superflous "MODCLUSTER000033: Failed to interrupt socket reception" on shutdown

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-460?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-460: -------------------------------------- Fix Version/s: 1.3.4.Final (was: 1.3.3.Final) > Silence superflous "MODCLUSTER000033: Failed to interrupt socket reception" on shutdown > --------------------------------------------------------------------------------------- > > Key: MODCLUSTER-460 > URL: https://issues.jboss.org/browse/MODCLUSTER-460 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 1.3.4.Final > > > This seems to be caused by the legacy code in mod_cluster, which could instead make use of interruptible channels introduced since JDK 1.4. Simpler option would be log this message onto debug. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-501) mod_proxy_cluster crash when using BalancerMember

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-501?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-501: -------------------------------------- Fix Version/s: 1.3.4.Final (was: 1.3.3.Final) > mod_proxy_cluster crash when using BalancerMember > ------------------------------------------------- > > Key: MODCLUSTER-501 > URL: https://issues.jboss.org/browse/MODCLUSTER-501 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final > Environment: o.s.:: CentOS Linux release 7.2.1511 > httpd 2.4.6 > mod cluster 1.3.1 final > Reporter: Paolo Lutterotti > Assignee: Michal Karm Babacek > Fix For: 1.3.4.Final > > Attachments: httpd.conf, modules.txt, vhost.conf, vhost.conf > > > Hello, > I'm experiencing an issue very similar to https://issues.jboss.org/browse/MODCLUSTER-356 > When I try to use a BalancerMember directive, I get a segmentation fault, caused at line https://github.com/modcluster/mod_cluster/blob/1.3.1.Final/native/mod_pro... > I tried to remove directives from the virtual host, but the issue persists until there is at least one ProxyPass using a balancer defined with BalancerMember. I attach a .conf file where I put all of the configurations involved in the issue and which is causing the crash. > If I put a check at line 2223, there are no more segmentations, but a 503 caused by mod_proxy_cluster.c(2332): proxy: byrequests balancer FAILED > Thanks, > Paolo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-505) ProxyErrorOverride=On causes workers in error state after 500 errors

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-505?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-505: -------------------------------------- Fix Version/s: 1.3.4.Final (was: 1.3.3.Final) > ProxyErrorOverride=On causes workers in error state after 500 errors > --------------------------------------------------------------------- > > Key: MODCLUSTER-505 > URL: https://issues.jboss.org/browse/MODCLUSTER-505 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.2.Final, 1.2.12.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.14.Final, 1.3.4.Final > > > When a VirtualHost uses ProxyPass to proxy traffic to the backend and uses ProxyErrorOverride to host custom error pages on Apache httpd side, when the backend replies with a 50x error code mod_proxy/mod_cluster marks that worker as down, breaking session stickiness. This behaviour is quite similar to have failonstatus=500 for example. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-508) &balancer->name[11], because of default: balancer://mycluster: Change magic number 11 to something meaningful

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-508?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-508: -------------------------------------- Fix Version/s: 1.3.4.Final (was: 1.3.3.Final) > &balancer->name[11], because of default: balancer://mycluster: Change magic number 11 to something meaningful > ------------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-508 > URL: https://issues.jboss.org/browse/MODCLUSTER-508 > Project: mod_cluster > Issue Type: Enhancement > Components: Native (httpd modules) > Affects Versions: 1.3.2.Final, 1.2.13.Final > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > Priority: Trivial > Fix For: 1.3.4.Final > > > While we compare balancers URL char by char, we start at index 11, because > the default beginning: {{balancer://}} is always there. It would be nice to change 11 to a named constant so as it is clear why it's 11 without debugger :) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues July 2016