June 2016 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-346) :read-proxies-configuration and :read-proxies-info fail when there is no httpd

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-346?page=com.atlassian.jira.pl... ] Radoslav Husar reassigned MODCLUSTER-346: ----------------------------------------- Assignee: Radoslav Husar (was: Jean-Frederic Clere) > :read-proxies-configuration and :read-proxies-info fail when there is no httpd > ------------------------------------------------------------------------------ > > Key: MODCLUSTER-346 > URL: https://issues.jboss.org/browse/MODCLUSTER-346 > Project: mod_cluster > Issue Type: Bug > Environment: RHEL 6, EAP 6.1.0, mod_cluster-1.2.4-1.Final_redhat_1.ep6.el6.noarch, > Reporter: Kristina Clair > Assignee: Radoslav Husar > > When the modcluster subsystem is unable to connect to a proxy, the jboss-cli commands :read-proxies-configuration and :read-proxies-info fail with an unhelpful error. > On both the domain controller and application host, :read-proxies-info and :read-proxies-configuration fail with the same error. This is the output from the application host: > {noformat} > [domain@localhost:9999 subsystem=modcluster] pwd > /host=localhost/server=cluster2/subsystem=modcluster > [domain@localhost:9999 subsystem=modcluster] :list-proxies > { > "outcome" => "success", > "result" => [ > "web02:8009", > "web01:8009" > ] > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-configuration > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-info > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > {noformat} > In the above example, modcluster was not able to connect to the proxies due to an ssl misconfiguration in the modcluster subsystem in domain.xml. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-346) :read-proxies-configuration and :read-proxies-info fail when there is no httpd

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-346?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-346: -------------------------------------- Bugzilla Update: (was: Perform) > :read-proxies-configuration and :read-proxies-info fail when there is no httpd > ------------------------------------------------------------------------------ > > Key: MODCLUSTER-346 > URL: https://issues.jboss.org/browse/MODCLUSTER-346 > Project: mod_cluster > Issue Type: Bug > Environment: RHEL 6, EAP 6.1.0, mod_cluster-1.2.4-1.Final_redhat_1.ep6.el6.noarch, > Reporter: Kristina Clair > Assignee: Jean-Frederic Clere > > When the modcluster subsystem is unable to connect to a proxy, the jboss-cli commands :read-proxies-configuration and :read-proxies-info fail with an unhelpful error. > On both the domain controller and application host, :read-proxies-info and :read-proxies-configuration fail with the same error. This is the output from the application host: > {noformat} > [domain@localhost:9999 subsystem=modcluster] pwd > /host=localhost/server=cluster2/subsystem=modcluster > [domain@localhost:9999 subsystem=modcluster] :list-proxies > { > "outcome" => "success", > "result" => [ > "web02:8009", > "web01:8009" > ] > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-configuration > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-info > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > {noformat} > In the above example, modcluster was not able to connect to the proxies due to an ssl misconfiguration in the modcluster subsystem in domain.xml. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-346) :read-proxies-configuration and :read-proxies-info fail when there is no httpd

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-346?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on MODCLUSTER-346: ---------------------------------------------------- Aaron Ogburn <aogburn(a)redhat.com> changed the Status of [bug 1343633|https://bugzilla.redhat.com/show_bug.cgi?id=1343633] from NEW to ASSIGNED > :read-proxies-configuration and :read-proxies-info fail when there is no httpd > ------------------------------------------------------------------------------ > > Key: MODCLUSTER-346 > URL: https://issues.jboss.org/browse/MODCLUSTER-346 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.4.Final > Environment: RHEL 6, EAP 6.1.0, mod_cluster-1.2.4-1.Final_redhat_1.ep6.el6.noarch, > Reporter: Kristina Clair > Assignee: Jean-Frederic Clere > > When the modcluster subsystem is unable to connect to a proxy, the jboss-cli commands :read-proxies-configuration and :read-proxies-info fail with an unhelpful error. > On both the domain controller and application host, :read-proxies-info and :read-proxies-configuration fail with the same error. This is the output from the application host: > {noformat} > [domain@localhost:9999 subsystem=modcluster] pwd > /host=localhost/server=cluster2/subsystem=modcluster > [domain@localhost:9999 subsystem=modcluster] :list-proxies > { > "outcome" => "success", > "result" => [ > "web02:8009", > "web01:8009" > ] > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-configuration > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-info > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > {noformat} > In the above example, modcluster was not able to connect to the proxies due to an ssl misconfiguration in the modcluster subsystem in domain.xml. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-346) :read-proxies-configuration and :read-proxies-info fail when there is no httpd

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-346?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated MODCLUSTER-346: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1343633 Bugzilla Update: Perform > :read-proxies-configuration and :read-proxies-info fail when there is no httpd > ------------------------------------------------------------------------------ > > Key: MODCLUSTER-346 > URL: https://issues.jboss.org/browse/MODCLUSTER-346 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.4.Final > Environment: RHEL 6, EAP 6.1.0, mod_cluster-1.2.4-1.Final_redhat_1.ep6.el6.noarch, > Reporter: Kristina Clair > Assignee: Jean-Frederic Clere > > When the modcluster subsystem is unable to connect to a proxy, the jboss-cli commands :read-proxies-configuration and :read-proxies-info fail with an unhelpful error. > On both the domain controller and application host, :read-proxies-info and :read-proxies-configuration fail with the same error. This is the output from the application host: > {noformat} > [domain@localhost:9999 subsystem=modcluster] pwd > /host=localhost/server=cluster2/subsystem=modcluster > [domain@localhost:9999 subsystem=modcluster] :list-proxies > { > "outcome" => "success", > "result" => [ > "web02:8009", > "web01:8009" > ] > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-configuration > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-info > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > {noformat} > In the above example, modcluster was not able to connect to the proxies due to an ssl misconfiguration in the modcluster subsystem in domain.xml. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-466) mod_cluster undersizes the connection pool on httpd 2.2

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-466?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on MODCLUSTER-466: ---------------------------------------------------- Jean-frederic Clere <jclere(a)redhat.com> changed the Status of [bug 1338642|https://bugzilla.redhat.com/show_bug.cgi?id=1338642] from NEW to MODIFIED > mod_cluster undersizes the connection pool on httpd 2.2 > ------------------------------------------------------- > > Key: MODCLUSTER-466 > URL: https://issues.jboss.org/browse/MODCLUSTER-466 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.3.2.Final, 1.2.13.Final > > > If all threads in a httpd child worker process are saturated with long requests, then all connections in the pool are exhausted, likely leaving none available for additional pings, which then fail with errors like: > [error] (70007)The timeout specified has expired: proxy: ajp: failed to acquire connection for ... > Documentation suggests the connection pool will be sized to ThreadsPerChild+1 to avoid that, but it looks like it is really just ThreadsPerChild on httpd 2.2. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-448) mod_cluster crashes apache thread if multiple nodes report the same AJP connect string

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-448?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-448: ------------------------------------------------ Having 2 JVMRoute and single IP/port looks like a configuration error we should reject the CONFIG message with an error. > mod_cluster crashes apache thread if multiple nodes report the same AJP connect string > -------------------------------------------------------------------------------------- > > Key: MODCLUSTER-448 > URL: https://issues.jboss.org/browse/MODCLUSTER-448 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Affects Versions: 1.2.6.Final > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > Fix For: 1.3.3.Final, 1.2.13.Final > > > Reported on behalf of [Toby Murray|https://github.com/ToeBee]: > Tracking issue #[138|https://github.com/modcluster/mod_cluster/issues/138] > Let's carry on with any discussion here, on JIRA... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-501) mod_proxy_cluster crash when using BalancerMember

by Paolo Lutterotti (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-501?page=com.atlassian.jira.pl... ] Paolo Lutterotti commented on MODCLUSTER-501: --------------------------------------------- Hi Michal, thanks for your interest. I attach my httpd.conf. Please note that all the stuff included from other directories (conf.d, vhosts.d) has been disabled, I just include the vhost.conf from my previous comment and listen80.conf which is only a set of Listen XYZ:80 directives. I also attach the list of currently loaded modules (mod cluster is now disabled) Yes, I'd like to use mod_cluster for my tomcat/jboss apps and balancerMember for drupal. Best. Paolo p.s. sorry, I attached vhost.conf twice > mod_proxy_cluster crash when using BalancerMember > ------------------------------------------------- > > Key: MODCLUSTER-501 > URL: https://issues.jboss.org/browse/MODCLUSTER-501 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final > Environment: o.s.:: CentOS Linux release 7.2.1511 > httpd 2.4.6 > mod cluster 1.3.1 final > Reporter: Paolo Lutterotti > Assignee: Michal Karm Babacek > Fix For: 1.3.3.Final > > Attachments: httpd.conf, modules.txt, vhost.conf, vhost.conf > > > Hello, > I'm experiencing an issue very similar to https://issues.jboss.org/browse/MODCLUSTER-356 > When I try to use a BalancerMember directive, I get a segmentation fault, caused at line https://github.com/modcluster/mod_cluster/blob/1.3.1.Final/native/mod_pro... > I tried to remove directives from the virtual host, but the issue persists until there is at least one ProxyPass using a balancer defined with BalancerMember. I attach a .conf file where I put all of the configurations involved in the issue and which is causing the crash. > If I put a check at line 2223, there are no more segmentations, but a 503 caused by mod_proxy_cluster.c(2332): proxy: byrequests balancer FAILED > Thanks, > Paolo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-501) mod_proxy_cluster crash when using BalancerMember

by Paolo Lutterotti (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-501?page=com.atlassian.jira.pl... ] Paolo Lutterotti updated MODCLUSTER-501: ---------------------------------------- Attachment: modules.txt > mod_proxy_cluster crash when using BalancerMember > ------------------------------------------------- > > Key: MODCLUSTER-501 > URL: https://issues.jboss.org/browse/MODCLUSTER-501 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final > Environment: o.s.:: CentOS Linux release 7.2.1511 > httpd 2.4.6 > mod cluster 1.3.1 final > Reporter: Paolo Lutterotti > Assignee: Michal Karm Babacek > Fix For: 1.3.3.Final > > Attachments: httpd.conf, modules.txt, vhost.conf, vhost.conf > > > Hello, > I'm experiencing an issue very similar to https://issues.jboss.org/browse/MODCLUSTER-356 > When I try to use a BalancerMember directive, I get a segmentation fault, caused at line https://github.com/modcluster/mod_cluster/blob/1.3.1.Final/native/mod_pro... > I tried to remove directives from the virtual host, but the issue persists until there is at least one ProxyPass using a balancer defined with BalancerMember. I attach a .conf file where I put all of the configurations involved in the issue and which is causing the crash. > If I put a check at line 2223, there are no more segmentations, but a 503 caused by mod_proxy_cluster.c(2332): proxy: byrequests balancer FAILED > Thanks, > Paolo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-501) mod_proxy_cluster crash when using BalancerMember

by Paolo Lutterotti (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-501?page=com.atlassian.jira.pl... ] Paolo Lutterotti updated MODCLUSTER-501: ---------------------------------------- Attachment: vhost.conf > mod_proxy_cluster crash when using BalancerMember > ------------------------------------------------- > > Key: MODCLUSTER-501 > URL: https://issues.jboss.org/browse/MODCLUSTER-501 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final > Environment: o.s.:: CentOS Linux release 7.2.1511 > httpd 2.4.6 > mod cluster 1.3.1 final > Reporter: Paolo Lutterotti > Assignee: Michal Karm Babacek > Fix For: 1.3.3.Final > > Attachments: httpd.conf, vhost.conf, vhost.conf > > > Hello, > I'm experiencing an issue very similar to https://issues.jboss.org/browse/MODCLUSTER-356 > When I try to use a BalancerMember directive, I get a segmentation fault, caused at line https://github.com/modcluster/mod_cluster/blob/1.3.1.Final/native/mod_pro... > I tried to remove directives from the virtual host, but the issue persists until there is at least one ProxyPass using a balancer defined with BalancerMember. I attach a .conf file where I put all of the configurations involved in the issue and which is causing the crash. > If I put a check at line 2223, there are no more segmentations, but a 503 caused by mod_proxy_cluster.c(2332): proxy: byrequests balancer FAILED > Thanks, > Paolo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-501) mod_proxy_cluster crash when using BalancerMember

by Paolo Lutterotti (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-501?page=com.atlassian.jira.pl... ] Paolo Lutterotti updated MODCLUSTER-501: ---------------------------------------- Attachment: httpd.conf > mod_proxy_cluster crash when using BalancerMember > ------------------------------------------------- > > Key: MODCLUSTER-501 > URL: https://issues.jboss.org/browse/MODCLUSTER-501 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final > Environment: o.s.:: CentOS Linux release 7.2.1511 > httpd 2.4.6 > mod cluster 1.3.1 final > Reporter: Paolo Lutterotti > Assignee: Michal Karm Babacek > Fix For: 1.3.3.Final > > Attachments: httpd.conf, vhost.conf, vhost.conf > > > Hello, > I'm experiencing an issue very similar to https://issues.jboss.org/browse/MODCLUSTER-356 > When I try to use a BalancerMember directive, I get a segmentation fault, caused at line https://github.com/modcluster/mod_cluster/blob/1.3.1.Final/native/mod_pro... > I tried to remove directives from the virtual host, but the issue persists until there is at least one ProxyPass using a balancer defined with BalancerMember. I attach a .conf file where I put all of the configurations involved in the issue and which is causing the crash. > If I put a check at line 2223, there are no more segmentations, but a 503 caused by mod_proxy_cluster.c(2332): proxy: byrequests balancer FAILED > Thanks, > Paolo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 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