December 2016 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-363) Rather unsettling warnings in Solaris build logs

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-363?page=com.atlassian.jira.pl... ] Michal Karm Babacek reassigned MODCLUSTER-363: ---------------------------------------------- Assignee: George Zaronikas (was: Jean-Frederic Clere) > Rather unsettling warnings in Solaris build logs > ------------------------------------------------ > > Key: MODCLUSTER-363 > URL: https://issues.jboss.org/browse/MODCLUSTER-363 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.6.Final > Environment: Solaris sparc, x86 > Reporter: Michal Karm Babacek > Assignee: George Zaronikas > Fix For: 1.2.14.Final > > > Configure and compilation steps e.g. in these builds: [mod_cluster-solaris10-sparc64|https://jenkins.mw.lab.eng.bos.redhat.com/h...] and [mod_cluster-solaris10-x86|https://jenkins.mw.lab.eng.bos.redhat.com/hudso...]. > Bugspotter: [~vtunka] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-343) mod_cluster shouldn't overwrite stickysession=XXX|xxx from ProxyPass directives...

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-343?page=com.atlassian.jira.pl... ] Michal Karm Babacek commented on MODCLUSTER-343: ------------------------------------------------ Doesn't it because of MODCLUSTER-430? > mod_cluster shouldn't overwrite stickysession=XXX|xxx from ProxyPass directives... > ---------------------------------------------------------------------------------- > > Key: MODCLUSTER-343 > URL: https://issues.jboss.org/browse/MODCLUSTER-343 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-514) MemManagerFile doesn't take relative paths

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-514?page=com.atlassian.jira.pl... ] Michal Karm Babacek commented on MODCLUSTER-514: ------------------------------------------------ Minor -> Major, as it keeps causing problems and confusion. > MemManagerFile doesn't take relative paths > ------------------------------------------ > > Key: MODCLUSTER-514 > URL: https://issues.jboss.org/browse/MODCLUSTER-514 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final, 1.2.13.Final > Reporter: Michal Karm Babacek > Assignee: George Zaronikas > > This is mostly a user experience issue. > According to what {{LoadModule}} and other directives do, one would expect that a path without leading slash is a relative one to the server root. > h3. Setting > * {{MemManagerFile cache/mod_cluster}} > * {{ServerRoot "/home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build"}} > h3. Expected result > {noformat} > /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/cache/mod_cluster/ > manager.balancer.balancers manager.context.contexts manager.domain.domain manager.host.hosts manager.node.nodes > manager.balancer.balancers.lock manager.context.contexts.lock manager.domain.domain.lock manager.host.hosts.lock manager.node.nodes.lock > manager.balancer.balancers.slotmem manager.context.contexts.slotmem manager.domain.domain.slotmem manager.host.hosts.slotmem manager.node.nodes.slotmem > {noformat} > h3. Actual result > {noformat} > /cache/mod_cluster/ > manager.balancer.balancers manager.context.contexts manager.domain.domain manager.host.hosts manager.node.nodes > manager.balancer.balancers.lock manager.context.contexts.lock manager.domain.domain.lock manager.host.hosts.lock manager.node.nodes.lock > manager.balancer.balancers.slotmem manager.context.contexts.slotmem manager.domain.domain.slotmem manager.host.hosts.slotmem manager.node.nodes.slotmem > {noformat} > and an empty directory is created in the directory from which the httpd root process was started: > {{/home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/bin/cache/mod_cluster/}}. > h3. Fix > * leading {{/}} should mean absolute path > * without leading {{/}} should be relative to ServerRoot -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-514) MemManagerFile doesn't take relative paths

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-514?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-514: ------------------------------------------- Priority: Major (was: Minor) > MemManagerFile doesn't take relative paths > ------------------------------------------ > > Key: MODCLUSTER-514 > URL: https://issues.jboss.org/browse/MODCLUSTER-514 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final, 1.2.13.Final > Reporter: Michal Karm Babacek > Assignee: George Zaronikas > > This is mostly a user experience issue. > According to what {{LoadModule}} and other directives do, one would expect that a path without leading slash is a relative one to the server root. > h3. Setting > * {{MemManagerFile cache/mod_cluster}} > * {{ServerRoot "/home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build"}} > h3. Expected result > {noformat} > /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/cache/mod_cluster/ > manager.balancer.balancers manager.context.contexts manager.domain.domain manager.host.hosts manager.node.nodes > manager.balancer.balancers.lock manager.context.contexts.lock manager.domain.domain.lock manager.host.hosts.lock manager.node.nodes.lock > manager.balancer.balancers.slotmem manager.context.contexts.slotmem manager.domain.domain.slotmem manager.host.hosts.slotmem manager.node.nodes.slotmem > {noformat} > h3. Actual result > {noformat} > /cache/mod_cluster/ > manager.balancer.balancers manager.context.contexts manager.domain.domain manager.host.hosts manager.node.nodes > manager.balancer.balancers.lock manager.context.contexts.lock manager.domain.domain.lock manager.host.hosts.lock manager.node.nodes.lock > manager.balancer.balancers.slotmem manager.context.contexts.slotmem manager.domain.domain.slotmem manager.host.hosts.slotmem manager.node.nodes.slotmem > {noformat} > and an empty directory is created in the directory from which the httpd root process was started: > {{/home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/bin/cache/mod_cluster/}}. > h3. Fix > * leading {{/}} should mean absolute path > * without leading {{/}} should be relative to ServerRoot -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-514) MemManagerFile doesn't take relative paths

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-514?page=com.atlassian.jira.pl... ] Michal Karm Babacek commented on MODCLUSTER-514: ------------------------------------------------ Assigning to [~gzaronikas]. It is not a "hot potato" issue; I'm just load balancing work. THX. > MemManagerFile doesn't take relative paths > ------------------------------------------ > > Key: MODCLUSTER-514 > URL: https://issues.jboss.org/browse/MODCLUSTER-514 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final, 1.2.13.Final > Reporter: Michal Karm Babacek > Assignee: George Zaronikas > Priority: Minor > > This is mostly a user experience issue. > According to what {{LoadModule}} and other directives do, one would expect that a path without leading slash is a relative one to the server root. > h3. Setting > * {{MemManagerFile cache/mod_cluster}} > * {{ServerRoot "/home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build"}} > h3. Expected result > {noformat} > /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/cache/mod_cluster/ > manager.balancer.balancers manager.context.contexts manager.domain.domain manager.host.hosts manager.node.nodes > manager.balancer.balancers.lock manager.context.contexts.lock manager.domain.domain.lock manager.host.hosts.lock manager.node.nodes.lock > manager.balancer.balancers.slotmem manager.context.contexts.slotmem manager.domain.domain.slotmem manager.host.hosts.slotmem manager.node.nodes.slotmem > {noformat} > h3. Actual result > {noformat} > /cache/mod_cluster/ > manager.balancer.balancers manager.context.contexts manager.domain.domain manager.host.hosts manager.node.nodes > manager.balancer.balancers.lock manager.context.contexts.lock manager.domain.domain.lock manager.host.hosts.lock manager.node.nodes.lock > manager.balancer.balancers.slotmem manager.context.contexts.slotmem manager.domain.domain.slotmem manager.host.hosts.slotmem manager.node.nodes.slotmem > {noformat} > and an empty directory is created in the directory from which the httpd root process was started: > {{/home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/bin/cache/mod_cluster/}}. > h3. Fix > * leading {{/}} should mean absolute path > * without leading {{/}} should be relative to ServerRoot -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-514) MemManagerFile doesn't take relative paths

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-514?page=com.atlassian.jira.pl... ] Michal Karm Babacek reassigned MODCLUSTER-514: ---------------------------------------------- Assignee: George Zaronikas (was: Michal Karm Babacek) > MemManagerFile doesn't take relative paths > ------------------------------------------ > > Key: MODCLUSTER-514 > URL: https://issues.jboss.org/browse/MODCLUSTER-514 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final, 1.2.13.Final > Reporter: Michal Karm Babacek > Assignee: George Zaronikas > Priority: Minor > > This is mostly a user experience issue. > According to what {{LoadModule}} and other directives do, one would expect that a path without leading slash is a relative one to the server root. > h3. Setting > * {{MemManagerFile cache/mod_cluster}} > * {{ServerRoot "/home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build"}} > h3. Expected result > {noformat} > /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/cache/mod_cluster/ > manager.balancer.balancers manager.context.contexts manager.domain.domain manager.host.hosts manager.node.nodes > manager.balancer.balancers.lock manager.context.contexts.lock manager.domain.domain.lock manager.host.hosts.lock manager.node.nodes.lock > manager.balancer.balancers.slotmem manager.context.contexts.slotmem manager.domain.domain.slotmem manager.host.hosts.slotmem manager.node.nodes.slotmem > {noformat} > h3. Actual result > {noformat} > /cache/mod_cluster/ > manager.balancer.balancers manager.context.contexts manager.domain.domain manager.host.hosts manager.node.nodes > manager.balancer.balancers.lock manager.context.contexts.lock manager.domain.domain.lock manager.host.hosts.lock manager.node.nodes.lock > manager.balancer.balancers.slotmem manager.context.contexts.slotmem manager.domain.domain.slotmem manager.host.hosts.slotmem manager.node.nodes.slotmem > {noformat} > and an empty directory is created in the directory from which the httpd root process was started: > {{/home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/bin/cache/mod_cluster/}}. > h3. Fix > * leading {{/}} should mean absolute path > * without leading {{/}} should be relative to ServerRoot -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-557) Hot standby workers should be excluded from the deterministic failover candidate list

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-557?page=com.atlassian.jira.pl... ] Radoslav Husar edited comment on MODCLUSTER-557 at 12/14/16 4:55 AM: --------------------------------------------------------------------- Already done in Undertow with the initial implementation (since 1.4.7.Final). was (Author: rhusar): Already done in Undertow with the 1st implementation. > Hot standby workers should be excluded from the deterministic failover candidate list > ------------------------------------------------------------------------------------- > > Key: MODCLUSTER-557 > URL: https://issues.jboss.org/browse/MODCLUSTER-557 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.6.Final > > > We need to consider hot standby nodes, when there are only standby nodes in cluster and exclude from the initial candidate list. > No affected version, its master/1.3.6.Final-SNAPSHOT. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-557) Hot standby workers should be excluded from the deterministic failover candidate list

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-557?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-557: ------------------------------------------- Already done in Undertow with the 1st implementation. > Hot standby workers should be excluded from the deterministic failover candidate list > ------------------------------------------------------------------------------------- > > Key: MODCLUSTER-557 > URL: https://issues.jboss.org/browse/MODCLUSTER-557 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.6.Final > > > We need to consider hot standby nodes, when there are only standby nodes in cluster and exclude from the initial candidate list. > No affected version, its master/1.3.6.Final-SNAPSHOT. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-557) Hot standby workers should be excluded from the deterministic failover candidate list

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-557?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-557: -------------------------------------- Description: We need to consider hot standby nodes, when there are only standby nodes in cluster and exclude from the initial candidate list. No affected version, its master/1.3.6.Final-SNAPSHOT. was: We need to consider standby nodes, when there are only standby nodes in cluster and exclude from the initial candidate list. No affected version, its master/1.3.6.Final-SNAPSHOT. > Hot standby workers should be excluded from the deterministic failover candidate list > ------------------------------------------------------------------------------------- > > Key: MODCLUSTER-557 > URL: https://issues.jboss.org/browse/MODCLUSTER-557 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.6.Final > > > We need to consider hot standby nodes, when there are only standby nodes in cluster and exclude from the initial candidate list. > No affected version, its master/1.3.6.Final-SNAPSHOT. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-557) Hot standby workers should be excluded from the deterministic failover candidate list

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-557?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-557: -------------------------------------- Summary: Hot standby workers should be excluded from the deterministic failover candidate list (was: Standby workers should be excluded from the deterministic failover candidate list) > Hot standby workers should be excluded from the deterministic failover candidate list > ------------------------------------------------------------------------------------- > > Key: MODCLUSTER-557 > URL: https://issues.jboss.org/browse/MODCLUSTER-557 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.6.Final > > > We need to consider standby nodes, when there are only standby nodes in cluster and exclude from the initial candidate list. > No affected version, its master/1.3.6.Final-SNAPSHOT. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues December 2016