February 2014 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-362) configuration example for simple-load-provider has wrong attribute

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-362?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-362. -------------------------------------------- Fix Version/s: 1.2.8.Final Resolution: Done fixed. web page will be fixed next release. > configuration example for simple-load-provider has wrong attribute > ------------------------------------------------------------------ > > Key: MODCLUSTER-362 > URL: https://issues.jboss.org/browse/MODCLUSTER-362 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.0.Final > Reporter: Vittorio Rigamonti > Assignee: Jean-Frederic Clere > Priority: Minor > Fix For: 1.2.8.Final > > > The configuraton example in the gray box here: > http://docs.jboss.org/mod_cluster/1.2.0/html/java.AS7config.html#SimpleLo... > shoud be: > <simple-load-provider factor="1"/> > instead of > <simple-load-provider load="1"/> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-362) configuration example for simple-load-provider has wrong attribute

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-362?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-362: ------------------------------------------- Priority: Minor (was: Major) > configuration example for simple-load-provider has wrong attribute > ------------------------------------------------------------------ > > Key: MODCLUSTER-362 > URL: https://issues.jboss.org/browse/MODCLUSTER-362 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.0.Final > Reporter: Vittorio Rigamonti > Assignee: Jean-Frederic Clere > Priority: Minor > > The configuraton example in the gray box here: > http://docs.jboss.org/mod_cluster/1.2.0/html/java.AS7config.html#SimpleLo... > shoud be: > <simple-load-provider factor="1"/> > instead of > <simple-load-provider load="1"/> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-369) httpd should remove lost node/worker

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-369?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-369: ------------------------------------------- Priority: Minor (was: Major) > httpd should remove lost node/worker > ------------------------------------ > > Key: MODCLUSTER-369 > URL: https://issues.jboss.org/browse/MODCLUSTER-369 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.0.Final, 1.2.6.Final > Environment: httpd 2.2.24+tomcat 7.0.37 > Reporter: Stefano Nichele > Assignee: Jean-Frederic Clere > Priority: Minor > Attachments: httpd-error.log > > > supposing this env running on amazon: > - one virtual machine running HTTPD (let's call it FE) > - two virtual machines running tomcat (let's call them NODE01 and NODE02) > If NODE02 virtual machine dies or crash for any reason, HTTPD still report it in mod_cluster-manager sometime view with status ok and sometime with status notok. > Moreover some requests are still sent to the dead node. > Please note i replicated this behavior just closing netwrok traffic using iptables on NODE02: > iptables -A OUTPUT -p tcp -m state --state NEW,ESTABLISHED -m tcp --dport 6666 -j DROP > iptables -A INPUT -m state --state NEW,ESTABLISHED -p tcp --dport 8009 -j DROP > In this way tomcat instance is not able to send its status and HTTPD is not able to sends traffic on port 8009. > In my opinion two issues here: > 1. if HTTPD doesn't recevice any STATUS from a worker, the worker mustb e at least marked as NOTOK > 2. it seems that HTTPD considers the worker available during its retry policy and this causes that some requests are still forwarded to that node and it causes the worker appears as flapping. > Original threads:https://community.jboss.org/thread/234235 > Marking this is as critical since amazon is one of the main player in virtualization and if on a production environment an instance disappears (it can happen in any moment) the whole production environemnet is affected (since some requests are still send to the dead node). > In attahcment httpd error log file produced using modcluster 1.2.6. > at 08:32:30 HTTPD has been restarted (with two wrokers OK) > at 08:33:10 instance NODE02 (IP: 10.2.2.2) disappears > at 08:33:25 NODE2 is marked as NOTOK > at 08:33:32 NODE02 is marked as OK > at 08:33:41 NODE2 is marked as NOTOK > ...and so on... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-373) [mod_cluster] - mod_proxy_cluster.c:3325: possible bad if test ?‏

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-373?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-373. -------------------------------------------- Fix Version/s: 1.3.0.Alpha2 1.2.8.Final Resolution: Done Fixed in both branches. > [mod_cluster] - mod_proxy_cluster.c:3325: possible bad if test ?‏ > ----------------------------------------------------------------- > > Key: MODCLUSTER-373 > URL: https://issues.jboss.org/browse/MODCLUSTER-373 > Project: mod_cluster > Issue Type: Bug > Environment: Linux > Reporter: David Binderman > Assignee: Jean-Frederic Clere > Fix For: 1.3.0.Alpha2, 1.2.8.Final > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Source code file is ../BUILD/mod_cluster-1.2.6.Final/native/mod_proxy_cluster/mod_proxy_cluster.c > Source code lines are > while (*path !='&' || *path !='\0') > path++; > Suggest swap || for && -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-378) Use 'ap_unixd_config' instead of 'unixd_config' (apache >= 2.4)

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-378?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-378. -------------------------------------------- Resolution: Rejected The code uses: ++++ #if MODULE_MAGIC_NUMBER_MAJOR > 20081212 shmbuf.shm_perm.uid = ap_unixd_config.user_id; shmbuf.shm_perm.gid = ap_unixd_config.group_id; #else shmbuf.shm_perm.uid = unixd_config.user_id; shmbuf.shm_perm.gid = unixd_config.group_id; #endif +++ So that is godd. > Use 'ap_unixd_config' instead of 'unixd_config' (apache >= 2.4) > --------------------------------------------------------------- > > Key: MODCLUSTER-378 > URL: https://issues.jboss.org/browse/MODCLUSTER-378 > Project: mod_cluster > Issue Type: Task > Affects Versions: 1.2.6.Final > Reporter: Michaël Mathieu > Assignee: Jean-Frederic Clere > > Since Apache 2.4, they use ap_unixd_config instead of unixd_config. > Cf. http://httpd.apache.org/docs/current/developer/new_api_2_4.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-380) Some serious log messages don't have id to identify them

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-380?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-380. -------------------------------------------- Resolution: Done fixed in both branches. > Some serious log messages don't have id to identify them > -------------------------------------------------------- > > Key: MODCLUSTER-380 > URL: https://issues.jboss.org/browse/MODCLUSTER-380 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.6.Final > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.3.0.Alpha2, 1.2.8.Final > > > As a part of logging unification tests for EAP I found: > modcluster/core/src/main/java/org/jboss/modcluster/load/metric/impl/AverageSystemLoadMetric.java > - 52 logger.warnf("%s is not supported on this system and will be disabled.", this.getClass().getSimpleName()); > modcluster/core/src/main/java/org/jboss/modcluster/load/metric/impl/SystemMemoryUsageLoadMetric.java > - 64 this.logger.warn(this.getClass().getSimpleName() + " requires com.sun.management.OperatingSystemMXBean."); > these should be moved to ModClusterLogger.java as well > (See BZ: 1008901) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-380) Some serious log messages don't have id to identify them

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-380?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-380: ------------------------------------------- Fix Version/s: 1.3.0.Alpha2 > Some serious log messages don't have id to identify them > -------------------------------------------------------- > > Key: MODCLUSTER-380 > URL: https://issues.jboss.org/browse/MODCLUSTER-380 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.6.Final > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.3.0.Alpha2, 1.2.8.Final > > > As a part of logging unification tests for EAP I found: > modcluster/core/src/main/java/org/jboss/modcluster/load/metric/impl/AverageSystemLoadMetric.java > - 52 logger.warnf("%s is not supported on this system and will be disabled.", this.getClass().getSimpleName()); > modcluster/core/src/main/java/org/jboss/modcluster/load/metric/impl/SystemMemoryUsageLoadMetric.java > - 64 this.logger.warn(this.getClass().getSimpleName() + " requires com.sun.management.OperatingSystemMXBean."); > these should be moved to ModClusterLogger.java as well > (See BZ: 1008901) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-224) when using tomcat manager webapp to stop/start an application the start is ignored by mod_cluster

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-224?page=com.atlassian.jira.pl... ] Jean-Frederic Clere closed MODCLUSTER-224. ------------------------------------------ Fix by https://github.com/modcluster/mod_cluster/commit/ae481bec099054cd2cdd5bb5... > when using tomcat manager webapp to stop/start an application the start is ignored by mod_cluster > ------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-224 > URL: https://issues.jboss.org/browse/MODCLUSTER-224 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.0.9, 1.1.1.Final > Environment: tomcat and manager webapp + any test webapp. > Reporter: Jean-Frederic Clere > Assignee: Paul Ferraro > Fix For: 1.0.11, 1.1.4.Final , 1.2.2.Final > > > See JBPAPP-6262 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-359) stickysession not working with httpd-2.4.6 / mod_cluster-1.2.5.Final

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-359?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-359. -------------------------------------------- Resolution: Done fixed by https://github.com/modcluster/mod_cluster/commit/f69616a32e28ca1b345337e4... > stickysession not working with httpd-2.4.6 / mod_cluster-1.2.5.Final > --------------------------------------------------------------------- > > Key: MODCLUSTER-359 > URL: https://issues.jboss.org/browse/MODCLUSTER-359 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.5.Final, 1.2.6.Final > Environment: OS. SLES-11-SP1 x86_64 > Reporter: Marco Danti > Assignee: Jean-Frederic Clere > Labels: httpd, mod_cluster, stickysession > Fix For: 1.3.0.Alpha2 > > Attachments: MODCLUSTER-359-debug-info.tar.gz, tses.war > > > Setup: HTTPD configured as reverse proxy / load balancer for two instances of JBOSS-AS-7.2.0.Final running in HA configuration on two separate nodes. > Consider the following configuration (defined inside my virtual hosts) > > <Proxy balancer://mycluster> > ProxySet stickysession=JSESSIONID|jsessionid > </Proxy> > On httpd-2.2.24 / mod_cluster-1.2.0.Final it shows the following behaviour: > - 'stickysession' is working as expected > After upgrading to httpd-2.4.6/mod_cluster-1.2.5.Final things are worse: > - 'stickysession' is ignored and any client request gets dispatched alternatively > to each one of the two JBoss servers (exactly as if lbmethod=byrequest were defined) > As a final consideration, I read in the docs that stickysession should be enabled by default in mod_cluster anyway, but that is not the case for me. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-359) stickysession not working with httpd-2.4.6 / mod_cluster-1.2.5.Final

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-359?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-359: ------------------------------------------- Fix Version/s: 1.3.0.Alpha2 (was: 1.2.8.Final) > stickysession not working with httpd-2.4.6 / mod_cluster-1.2.5.Final > --------------------------------------------------------------------- > > Key: MODCLUSTER-359 > URL: https://issues.jboss.org/browse/MODCLUSTER-359 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.5.Final, 1.2.6.Final > Environment: OS. SLES-11-SP1 x86_64 > Reporter: Marco Danti > Assignee: Jean-Frederic Clere > Labels: httpd, mod_cluster, stickysession > Fix For: 1.3.0.Alpha2 > > Attachments: MODCLUSTER-359-debug-info.tar.gz, tses.war > > > Setup: HTTPD configured as reverse proxy / load balancer for two instances of JBOSS-AS-7.2.0.Final running in HA configuration on two separate nodes. > Consider the following configuration (defined inside my virtual hosts) > > <Proxy balancer://mycluster> > ProxySet stickysession=JSESSIONID|jsessionid > </Proxy> > On httpd-2.2.24 / mod_cluster-1.2.0.Final it shows the following behaviour: > - 'stickysession' is working as expected > After upgrading to httpd-2.4.6/mod_cluster-1.2.5.Final things are worse: > - 'stickysession' is ignored and any client request gets dispatched alternatively > to each one of the two JBoss servers (exactly as if lbmethod=byrequest were defined) > As a final consideration, I read in the docs that stickysession should be enabled by default in mod_cluster anyway, but that is not the case for me. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues February 2014