June 2016 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-376) multiple workers with the same id following a tomcat crash/kill

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-376?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-376: ------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/189 > multiple workers with the same id following a tomcat crash/kill > --------------------------------------------------------------- > > Key: MODCLUSTER-376 > URL: https://issues.jboss.org/browse/MODCLUSTER-376 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.0.10, 1.2.11.Final > Environment: -JBoss Enterprise Web Server 1.0.2 > -mod_cluster 1.0.10.GA_CP04 > -Red Hat Enterprise Linux 5 > Reporter: Aaron Ogburn > Assignee: Michal Karm Babacek > Fix For: 1.2.13.Final > > Attachments: 131122.patch > > > Following a kill or crash of tomcat, multiple workers are seen for a single id when a new tomcat node reconnects and reuses the id from the previously crashed worker. > The STATUS's ping check sees the old crashed worker first for the id and so pings the wrong destination. Thus the ping fails, and load factor is not applied. The persistent -1 load state leads to 503s. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-376) multiple workers with the same id following a tomcat crash/kill

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-376?page=com.atlassian.jira.pl... ] Michal Karm Babacek commented on MODCLUSTER-376: ------------------------------------------------ Applied upstream on 1.2.x so far https://github.com/modcluster/mod_cluster/pull/189 > multiple workers with the same id following a tomcat crash/kill > --------------------------------------------------------------- > > Key: MODCLUSTER-376 > URL: https://issues.jboss.org/browse/MODCLUSTER-376 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.0.10, 1.2.11.Final > Environment: -JBoss Enterprise Web Server 1.0.2 > -mod_cluster 1.0.10.GA_CP04 > -Red Hat Enterprise Linux 5 > Reporter: Aaron Ogburn > Assignee: Michal Karm Babacek > Fix For: 1.2.13.Final > > Attachments: 131122.patch > > > Following a kill or crash of tomcat, multiple workers are seen for a single id when a new tomcat node reconnects and reuses the id from the previously crashed worker. > The STATUS's ping check sees the old crashed worker first for the id and so pings the wrong destination. Thus the ping fails, and load factor is not applied. The persistent -1 load state leads to 503s. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-376) multiple workers with the same id following a tomcat crash/kill

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-376?page=com.atlassian.jira.pl... ] Michal Karm Babacek reassigned MODCLUSTER-376: ---------------------------------------------- Assignee: Michal Karm Babacek (was: Jean-Frederic Clere) > multiple workers with the same id following a tomcat crash/kill > --------------------------------------------------------------- > > Key: MODCLUSTER-376 > URL: https://issues.jboss.org/browse/MODCLUSTER-376 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.0.10, 1.2.11.Final > Environment: -JBoss Enterprise Web Server 1.0.2 > -mod_cluster 1.0.10.GA_CP04 > -Red Hat Enterprise Linux 5 > Reporter: Aaron Ogburn > Assignee: Michal Karm Babacek > Fix For: 1.2.13.Final > > Attachments: 131122.patch > > > Following a kill or crash of tomcat, multiple workers are seen for a single id when a new tomcat node reconnects and reuses the id from the previously crashed worker. > The STATUS's ping check sees the old crashed worker first for the id and so pings the wrong destination. Thus the ping fails, and load factor is not applied. The persistent -1 load state leads to 503s. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-509) excludedContexts attribut doesn't work for all Tomcat's VirtualHosts

by Michal Karm Babacek (JIRA)

Michal Karm Babacek created MODCLUSTER-509: ---------------------------------------------- Summary: excludedContexts attribut doesn't work for all Tomcat's VirtualHosts Key: MODCLUSTER-509 URL: https://issues.jboss.org/browse/MODCLUSTER-509 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.12.Final, 1.3.2.Final, 2.0.0.Alpha1 Environment: Tomcat8 (haven't tried elsewhere yet); mod_cluster version 2.0.0.Alpha1-SNAPSHOT Reporter: Michal Karm Babacek Assignee: Radoslav Husar Priority: Critical Fix For: 1.3.3.Final, 2.0.0.Alpha1 With the following configuration: {code} <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" advertiseGroupAddress="224.0.1.105" advertisePort="23364" advertiseInterface="10.40.4.50" excludedContexts="ROOT,docs,manager,host-manager,examples" /> {code} And these contexts in webapps: {code} clusterbench docs examples host-manager manager ROOT {code} One expects this output on Mod_cluster manger console: {code} Virtual Host 1: Contexts: /clusterbench, Status: ENABLED Request: 0 Disable Stop Aliases: localhost {code} It works, unless you configure additional VirtualHosts: {code} <Host name="LOCALHOST" appBase="webapps" unpackWARs="true" autoDeploy="true"> <Alias>LOCALHOST</Alias> <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="localhost_access_log" suffix=".txt" pattern="%h %l %u %t "%r" %s %b" /> </Host> <Host name="KARM.BRQ.REDHAT.COM" appBase="webapps" unpackWARs="true" autoDeploy="true"> <Alias>KARM.BRQ.REDHAT.COM</Alias> <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="localhost_access_log" suffix=".txt" pattern="%h %l %u %t "%r" %s %b" /> </Host> {code} result: {code} Node worker1 (ajp://10.40.4.50:8009): Enable Contexts Disable Contexts Stop Contexts Balancer: mycluster,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 1,Ttl: 60000000,Status: OK,Elected: 0,Read: 0,Transferred: 0,Connected: 0,Load: 100 Virtual Host 2: Contexts: /docs, Status: ENABLED Request: 0 Disable Stop /manager, Status: ENABLED Request: 0 Disable Stop /host-manager, Status: ENABLED Request: 0 Disable Stop /examples, Status: ENABLED Request: 0 Disable Stop /, Status: ENABLED Request: 0 Disable Stop /clusterbench, Status: ENABLED Request: 0 Disable Stop Aliases: karm.brq.redhat.com Virtual Host 1: Contexts: /clusterbench, Status: ENABLED Request: 0 Disable Stop Aliases: localhost {code} I find this bug being of Critical priority, because it could coax users into believing they excluded certain context while in fact they didn't. WDYT? Is it possible to tweak with the Listener's configuration somehow? THX. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-397) StickySessions don't work for ProxyPass from unenabled context

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl... ] Michal Karm Babacek commented on MODCLUSTER-397: ------------------------------------------------ Done. 1.3.x Merged long time ago: https://github.com/modcluster/mod_cluster/pull/158 1.2.x Pending review: https://github.com/modcluster/mod_cluster/pull/188 > StickySessions don't work for ProxyPass from unenabled context > -------------------------------------------------------------- > > Key: MODCLUSTER-397 > URL: https://issues.jboss.org/browse/MODCLUSTER-397 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Michal Karm Babacek > Fix For: 1.3.3.Final, 1.2.13.Final > > > Sticky sessions are not maintained if you try to ProxyPass from an unenabled context to an enabled one. For example, consider JBoss with just /foo deployed and enabled via MCMP. Then try to ProxyPass / to /foo/ on httpd: > CreateBalancers 1 > ... > ProxyPass / balancer://mycluster/foo/ stickysession=JSESSIONID|jsessionid nofailover=On -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-397) StickySessions don't work for ProxyPass from unenabled context

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-397: ------------------------------------------- Git Pull Request: https://github.com/modcluster/mod_cluster/pull/188, https://github.com/modcluster/mod_cluster/pull/158/ (was: https://github.com/modcluster/mod_cluster/pull/188) > StickySessions don't work for ProxyPass from unenabled context > -------------------------------------------------------------- > > Key: MODCLUSTER-397 > URL: https://issues.jboss.org/browse/MODCLUSTER-397 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Michal Karm Babacek > Fix For: 1.3.3.Final, 1.2.13.Final > > > Sticky sessions are not maintained if you try to ProxyPass from an unenabled context to an enabled one. For example, consider JBoss with just /foo deployed and enabled via MCMP. Then try to ProxyPass / to /foo/ on httpd: > CreateBalancers 1 > ... > ProxyPass / balancer://mycluster/foo/ stickysession=JSESSIONID|jsessionid nofailover=On -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-397) StickySessions don't work for ProxyPass from unenabled context

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-397: ------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/188 > StickySessions don't work for ProxyPass from unenabled context > -------------------------------------------------------------- > > Key: MODCLUSTER-397 > URL: https://issues.jboss.org/browse/MODCLUSTER-397 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Michal Karm Babacek > Fix For: 1.3.3.Final, 1.2.13.Final > > > Sticky sessions are not maintained if you try to ProxyPass from an unenabled context to an enabled one. For example, consider JBoss with just /foo deployed and enabled via MCMP. Then try to ProxyPass / to /foo/ on httpd: > CreateBalancers 1 > ... > ProxyPass / balancer://mycluster/foo/ stickysession=JSESSIONID|jsessionid nofailover=On -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 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 commented on MODCLUSTER-439: ------------------------------------------- Needs to be rethinked, with last changes: sar is gone, jboss web is gone (so the directory needs to change), catalina-standalone will be gone, tomcat7 module will be gone. There is unnecessary releasing.txt, readme is missing, run demo is not executable, nor does it run, also fails on windows.. etc needs some care. {noformat} [rhusar@syrah client]$ ./run-demo.sh ./run-demo.sh: line 17: 6835 Bus error: 10 java -classpath $CP $OPTS org.jboss.modcluster.demo.client.ModClusterDemo {noformat} > 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: Feature Request > Components: Documentation & Demos > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > 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 (v6.4.11#64026)

7 years, 10 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 edited comment on MODCLUSTER-439 at 6/1/16 5:19 PM: ------------------------------------------------------------------- I would also like to move the distribution aspects of the project to /distribution (or /dist as wildfly?) and build the /sar and bundles there. was (Author: rhusar): I would also like to move the distribution aspects of the project to /distribution and build the /sar and bundles there. > 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: Feature Request > Components: Documentation & Demos > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > 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 (v6.4.11#64026)

7 years, 10 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: -------------------------------------- Summary: Installation for Tomcat 6/7/8 is cumbersome: revamp distribution profile (was: Installation for Tomcat 6/7/8 is cumbersome, revamp distribution profile) > 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: Feature Request > Components: Documentation & Demos > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > 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 (v6.4.11#64026)

7 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 June 2016