April 2019 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-686) Change use of HTTP download locations to HTTPS

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-686?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-686: -------------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/modcluster/docs.modcluster.io/pull/12 > Change use of HTTP download locations to HTTPS > ---------------------------------------------- > > Key: MODCLUSTER-686 > URL: https://issues.jboss.org/browse/MODCLUSTER-686 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java), Documentation & Demos > Affects Versions: 1.1.3.Final, 1.2.13.Final, 1.4.0.Final, 1.3.10.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Blocker > Fix For: 1.1.4.Final , 1.2.14.Final, 2.0.0.Alpha1, 1.4.1.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-685) Upgrade jboss-parent to 34

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-685?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-685: -------------------------------------- Git Pull Request: https://github.com/modcluster/mod_cluster/pull/371, https://github.com/modcluster/docs.modcluster.io/pull/12 (was: https://github.com/modcluster/mod_cluster/pull/371) > Upgrade jboss-parent to 34 > -------------------------- > > Key: MODCLUSTER-685 > URL: https://issues.jboss.org/browse/MODCLUSTER-685 > Project: mod_cluster > Issue Type: Component Upgrade > Affects Versions: 1.4.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 2.0.0.Alpha1, 1.4.1.Final > > > https://github.com/jboss/jboss-parent-pom/tree/jboss-parent-34 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-687) Ban non-https repositories

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-687?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-687: -------------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/modcluster/docs.modcluster.io/pull/12 > Ban non-https repositories > -------------------------- > > Key: MODCLUSTER-687 > URL: https://issues.jboss.org/browse/MODCLUSTER-687 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java), Documentation & Demos > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Follows up on MODCLUSTER-686. > {noformat} > <bannedRepositories> > <bannedRepositories>http://*</bannedRepositories> > <bannedPluginRepositories>http://*</bannedPluginRepositories> > </bannedRepositories> > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-430) CreateBalancers behave the same with option 0 or 2

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-430?page=com.atlassian.jira.pl... ] Jean-Frederic Clere edited comment on MODCLUSTER-430 at 4/11/19 11:43 AM: -------------------------------------------------------------------------- [~mbabacek] Please retest... I have tested with the following: +++ CreateBalancers 0 / 2 (try 0 or 2) <VirtualHost 10.36.116.185:8000> ServerName 10.36.116.185 ErrorLog "logs/error_log.10.36.116.185" CustomLog "logs/access_log.10.36.116.185" common ProxyRequests Off </VirtualHost> <VirtualHost 192.168.1.35:8000> ServerName 192.168.1.35 ErrorLog "logs/error_log.192.168.1.35" CustomLog "logs/access_log.192.168.1.35" common ProxyRequests Off </VirtualHost> +++ And it is working basically if you have no proxy directive in the VirtualHost the VirtualHost is ignored by mod_cluster... So the main server is used instead. was (Author: jfclere): [~mbabacek] Please retest... I have tested with the following: +++ CreateBalancers 0 / 2 # VirtualHost... <VirtualHost 10.36.116.185:8000> ServerName 10.36.116.185 ErrorLog "logs/error_log.10.36.116.185" CustomLog "logs/access_log.10.36.116.185" common ProxyRequests Off </VirtualHost> <VirtualHost 192.168.1.35:8000> ServerName 192.168.1.35 ErrorLog "logs/error_log.192.168.1.35" CustomLog "logs/access_log.192.168.1.35" common ProxyRequests Off </VirtualHost> +++ And it is working basically if you have no proxy directive in the VirtualHost the VirtualHost is ignored by mod_cluster... So the main server is used instead. > CreateBalancers behave the same with option 0 or 2 > -------------------------------------------------- > > Key: MODCLUSTER-430 > URL: https://issues.jboss.org/browse/MODCLUSTER-430 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final, 1.2.9.Final > Environment: RHEL 6.4.0 > Apache HTTPD 2.4.10 > JBoss 6.1.1 > Mod_cluster 1.3.0 Final > Reporter: John Jerome > Assignee: Michal Karm > Priority: Major > > The directive CreateBalancers with directive 0 or 2 creates the balancers on all httpd vhosts. > With option 2, the balancers should be created on the main server only, not in the vhosts. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-430) CreateBalancers behave the same with option 0 or 2

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-430?page=com.atlassian.jira.pl... ] Jean-Frederic Clere edited comment on MODCLUSTER-430 at 4/11/19 11:42 AM: -------------------------------------------------------------------------- [~mbabacek] Please retest... I have tested with the following: +++ CreateBalancers 0 / 2 # VirtualHost... <VirtualHost 10.36.116.185:8000> ServerName 10.36.116.185 ErrorLog "logs/error_log.10.36.116.185" CustomLog "logs/access_log.10.36.116.185" common ProxyRequests Off </VirtualHost> <VirtualHost 192.168.1.35:8000> ServerName 192.168.1.35 ErrorLog "logs/error_log.192.168.1.35" CustomLog "logs/access_log.192.168.1.35" common ProxyRequests Off </VirtualHost> +++ And it is working basically if you have no proxy directive in the VirtualHost the VirtualHost is ignored by mod_cluster... So the main server is used instead. was (Author: jfclere): [~mbabacek] Please retest... > CreateBalancers behave the same with option 0 or 2 > -------------------------------------------------- > > Key: MODCLUSTER-430 > URL: https://issues.jboss.org/browse/MODCLUSTER-430 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final, 1.2.9.Final > Environment: RHEL 6.4.0 > Apache HTTPD 2.4.10 > JBoss 6.1.1 > Mod_cluster 1.3.0 Final > Reporter: John Jerome > Assignee: Michal Karm > Priority: Major > > The directive CreateBalancers with directive 0 or 2 creates the balancers on all httpd vhosts. > With option 2, the balancers should be created on the main server only, not in the vhosts. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-430) CreateBalancers behave the same with option 0 or 2

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-430?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-430: ------------------------------------------------ [~mbabacek] Please retest... > CreateBalancers behave the same with option 0 or 2 > -------------------------------------------------- > > Key: MODCLUSTER-430 > URL: https://issues.jboss.org/browse/MODCLUSTER-430 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final, 1.2.9.Final > Environment: RHEL 6.4.0 > Apache HTTPD 2.4.10 > JBoss 6.1.1 > Mod_cluster 1.3.0 Final > Reporter: John Jerome > Assignee: Michal Karm > Priority: Major > > The directive CreateBalancers with directive 0 or 2 creates the balancers on all httpd vhosts. > With option 2, the balancers should be created on the main server only, not in the vhosts. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-576) CreateBalancers 1 ignored

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-576?page=com.atlassian.jira.pl... ] Jean-Frederic Clere closed MODCLUSTER-576. ------------------------------------------ Resolution: Cannot Reproduce Can't reproduce in 1.3.x nor 2.0.x > CreateBalancers 1 ignored > ------------------------- > > Key: MODCLUSTER-576 > URL: https://issues.jboss.org/browse/MODCLUSTER-576 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.6.Final > Environment: httpd 2.4.25 > Reporter: Antoine Cotten > Assignee: Jean-Frederic Clere > Priority: Major > > The documentation mentions: > bq. CreateBalancers > bq. 1 — Don’t create balancers (requires at least one ProxyPass/ProxyPassMatch to define the balancer names). > However using this option still creates balancers in every vhost. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-686) Change use of HTTP download locations to HTTPS

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-686?page=com.atlassian.jira.pl... ] Work on MODCLUSTER-686 started by Radoslav Husar. ------------------------------------------------- > Change use of HTTP download locations to HTTPS > ---------------------------------------------- > > Key: MODCLUSTER-686 > URL: https://issues.jboss.org/browse/MODCLUSTER-686 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java), Documentation & Demos > Affects Versions: 1.1.3.Final, 1.2.13.Final, 1.4.0.Final, 1.3.10.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Blocker > Fix For: 1.1.4.Final , 1.2.14.Final, 2.0.0.Alpha1, 1.4.1.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-687) Ban non-https repositories

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-687?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-687: ------------------------------------------- Other option is to upgrade jboss-parent with this change https://github.com/jboss/jboss-parent-pom/pull/63 once released. > Ban non-https repositories > -------------------------- > > Key: MODCLUSTER-687 > URL: https://issues.jboss.org/browse/MODCLUSTER-687 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java), Documentation & Demos > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Follows up on MODCLUSTER-686. > {noformat} > <bannedRepositories> > <bannedRepositories>http://*</bannedRepositories> > <bannedPluginRepositories>http://*</bannedPluginRepositories> > </bannedRepositories> > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-687) Ban non-https repositories

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-687?page=com.atlassian.jira.pl... ] Work on MODCLUSTER-687 started by Radoslav Husar. ------------------------------------------------- > Ban non-https repositories > -------------------------- > > Key: MODCLUSTER-687 > URL: https://issues.jboss.org/browse/MODCLUSTER-687 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java), Documentation & Demos > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Follows up on MODCLUSTER-686. > {noformat} > <bannedRepositories> > <bannedRepositories>http://*</bannedRepositories> > <bannedPluginRepositories>http://*</bannedPluginRepositories> > </bannedRepositories> > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues April 2019