June 2016 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-506) SegFault due to corrupt nodestatsmem

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-506?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-506: -------------------------------------- Priority: Critical (was: Major) > SegFault due to corrupt nodestatsmem > ------------------------------------ > > Key: MODCLUSTER-506 > URL: https://issues.jboss.org/browse/MODCLUSTER-506 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.12.Final > Environment: _redhat_2.ep6.el6.x86_64 > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > Priority: Critical > Fix For: 1.2.13.Final > > > See linked bugzillas, corrupted nodestatsmem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-410) OPTIONS call not returning available methods

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-410?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-410: -------------------------------------- Affects Version/s: 1.2.12.Final 1.3.2.Final > OPTIONS call not returning available methods > -------------------------------------------- > > Key: MODCLUSTER-410 > URL: https://issues.jboss.org/browse/MODCLUSTER-410 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.3.2.Final, 1.2.12.Final > Reporter: Roman Jurkov > Assignee: Jean-Frederic Clere > Priority: Minor > > options call returning just standard registered methods, that is because mod_cluster doesn't register methods through httpd api ap_method_register(). > by using apache api we can get free validation, and faster checks against method_number() instead of method name and strcmp(). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-410) OPTIONS call not returning available methods

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-410?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-410: -------------------------------------- Status: Open (was: Pull Request Sent) Git Pull Request: (was: https://github.com/modcluster/mod_cluster/pull/86) Fixing state, Roman's PR is at https://github.com/modcluster/mod_cluster/pull/86 > OPTIONS call not returning available methods > -------------------------------------------- > > Key: MODCLUSTER-410 > URL: https://issues.jboss.org/browse/MODCLUSTER-410 > Project: mod_cluster > Issue Type: Bug > Reporter: Roman Jurkov > Assignee: Jean-Frederic Clere > Priority: Minor > > options call returning just standard registered methods, that is because mod_cluster doesn't register methods through httpd api ap_method_register(). > by using apache api we can get free validation, and faster checks against method_number() instead of method name and strcmp(). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

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

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-397: -------------------------------------- Fix Version/s: 2.0.0.Alpha1 > 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, 2.0.0.Alpha1, 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)

8 years, 7 months

1
0
0 / 0

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

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-397: -------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done I am resolving this since everything is merged. > 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, 2.0.0.Alpha1, 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)

8 years, 7 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: -------------------------------------- Priority: Trivial (was: Minor) > &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: Bug > 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.3.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)

8 years, 7 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: -------------------------------------- Issue Type: Enhancement (was: Bug) > &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.3.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)

8 years, 7 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: -------------------------------------- Summary: &balancer->name[11], because of default: balancer://mycluster: Change magic number 11 to something meaningful (was: &balancer->name[11], becasue of default: balancer://mycluster: Change magic number 11 to something meaningful) > &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: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.2.Final, 1.2.13.Final > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > Priority: Minor > Fix For: 1.3.3.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)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-492) mod_cluster should allow failover of GET requests by default

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-492?page=com.atlassian.jira.pl... ] Radoslav Husar edited comment on MODCLUSTER-492 at 6/16/16 5:17 PM: -------------------------------------------------------------------- What exactly is here to do? * {{maxAttempts}} defaults to 1, so the native balancer *will* try another worker * {{stickySession*}} attributes are configurable on worker side... was (Author: mbabacek): What exactly is here to do? * {{maxAttempts}} defaults to 1, so the native balacner *will* try another worker * {{stickySession*}} attributes are configurable on worker side... > mod_cluster should allow failover of GET requests by default > ------------------------------------------------------------ > > Key: MODCLUSTER-492 > URL: https://issues.jboss.org/browse/MODCLUSTER-492 > Project: mod_cluster > Issue Type: Enhancement > Components: Core & Container Integration (Java), Native (httpd modules) > Affects Versions: 1.3.2.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > For any well developed web application, all GET requests should be idempotent and safe for failing over to another node. This should be default behavior, with a configuration option to disable it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-282) Add JGroups support

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-282?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-282: -------------------------------------- Component/s: Core & Container Integration (Java) Native (httpd modules) > Add JGroups support > ------------------- > > Key: MODCLUSTER-282 > URL: https://issues.jboss.org/browse/MODCLUSTER-282 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java), Native (httpd modules) > Affects Versions: 1.2.0.Final > Reporter: Jean-Frederic Clere > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > https://community.jboss.org/wiki/MOD-CLUSTERDiscoveryProtocol -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 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 June 2016