February 2015 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-451) UUID for auto-generated jvmRoute does not work with WildFly

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-451?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-451: ------------------------------------------- Neither the user should be using 0.0.0.0 in production, if there are multiple addresses to be used, they should be enumerated. > UUID for auto-generated jvmRoute does not work with WildFly > ----------------------------------------------------------- > > Key: MODCLUSTER-451 > URL: https://issues.jboss.org/browse/MODCLUSTER-451 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.0.Final > Environment: WildFly 8.2.0.Final, mod_cluster 1.3.0 > Reporter: Michal Babacek > Assignee: Radoslav Husar > Fix For: 1.3.1.Beta3 > > > It appears that UUID is not generated with WildFly/Undertow/mod_cluster setup. For example, if one does not set any instance-id/jvmRoute and binds to 0.0.0.0, one gets {{localhost}} jvmRoute Instead of a proper UUID. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-451) UUID for auto-generated jvmRoute does not work with WildFly

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-451?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-451. ------------------------------------- Resolution: Won't Fix Regarding "instance-id": O.K., thx for heads up. Regarding "0.0.0.0": Indeed you do, as long as the objective is to reproduce your user's env :-) MODCLUSTER-448 > UUID for auto-generated jvmRoute does not work with WildFly > ----------------------------------------------------------- > > Key: MODCLUSTER-451 > URL: https://issues.jboss.org/browse/MODCLUSTER-451 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.0.Final > Environment: WildFly 8.2.0.Final, mod_cluster 1.3.0 > Reporter: Michal Babacek > Assignee: Radoslav Husar > Fix For: 1.3.1.Beta3 > > > It appears that UUID is not generated with WildFly/Undertow/mod_cluster setup. For example, if one does not set any instance-id/jvmRoute and binds to 0.0.0.0, one gets {{localhost}} jvmRoute Instead of a proper UUID. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-452) mod_cluster with WildFly reports 0.0.0.0 to the balancer

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-452?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-452: -------------------------------------- Description: While I was working on [issue 138|https://github.com/modcluster/mod_cluster/issues/138] (MODCLUSTER-448), it came to my attention that one can't force EAP 6.4 Beta (jbossweb, mod_cluster 1.2.11) to send anything like {{ajp://0.0.0.0:8009}} to the balancer. If one sets the application server to bind to 0.0.0.0, mod_cluster core correctly guesses 127.0.0.1 and sends {{ajp://127.0.0.1:8009}} to the balancer. On the contrary, WildFly goes only half way: it reports 127.0.0.1 in the log: {noformat} [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000012: default-server connector will use /127.0.0.1 {noformat} and yet it sends 0.0.0.0 to the balancer: {noformat} Node localhost (ajp://0.0.0.0:8009): {noformat} Note the {{localhost}} string in place of properly generated UUID: MODCLUSTER-451. For some historical context, I suggest: MODCLUSTER-91 and MODCLUSTER-168 was: While I was working on [issue 138|https://github.com/modcluster/mod_cluster/issues/138] (MODCLUSTER-448), it came to my attention that one can't force EAP 6.4 Beta (jbossweb, mod_cluster 1.2.11) to send anything like {{ajp://0.0.0.0:8009}} to the balancer. If one sets the application server to bind to 0.0.0.0, mod_cluster core correctly guesses 127.0.0.1 and sends {{ajp:/127.0.0.1:8009}} to the balancer. On the contrary, WildFly goes only half way: it reports 127.0.0.1 in the log: {noformat} [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000012: default-server connector will use /127.0.0.1 {noformat} and yet it sends 0.0.0.0 to the balancer: {noformat} Node localhost (ajp://0.0.0.0:8009): {noformat} Note the {{localhost}} string in place of properly generated UUID: MODCLUSTER-451. For some historical context, I suggest: MODCLUSTER-91 and MODCLUSTER-168 > mod_cluster with WildFly reports 0.0.0.0 to the balancer > -------------------------------------------------------- > > Key: MODCLUSTER-452 > URL: https://issues.jboss.org/browse/MODCLUSTER-452 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.0.Final > Reporter: Michal Babacek > Assignee: Radoslav Husar > Fix For: 1.3.1.Beta3 > > > While I was working on [issue 138|https://github.com/modcluster/mod_cluster/issues/138] (MODCLUSTER-448), it came to my attention that one can't force EAP 6.4 Beta (jbossweb, mod_cluster 1.2.11) to send anything like {{ajp://0.0.0.0:8009}} to the balancer. If one sets the application server to bind to 0.0.0.0, mod_cluster core correctly guesses 127.0.0.1 and sends {{ajp://127.0.0.1:8009}} to the balancer. > On the contrary, WildFly goes only half way: it reports 127.0.0.1 in the log: > {noformat} > [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000012: default-server connector will use /127.0.0.1 > {noformat} > and yet it sends 0.0.0.0 to the balancer: > {noformat} > Node localhost (ajp://0.0.0.0:8009): > {noformat} > Note the {{localhost}} string in place of properly generated UUID: MODCLUSTER-451. > For some historical context, I suggest: MODCLUSTER-91 and MODCLUSTER-168 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-452) mod_cluster with WildFly reports 0.0.0.0 to the balancer

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-452?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-452: -------------------------------------- Fix Version/s: 1.3.1.Beta3 > mod_cluster with WildFly reports 0.0.0.0 to the balancer > -------------------------------------------------------- > > Key: MODCLUSTER-452 > URL: https://issues.jboss.org/browse/MODCLUSTER-452 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.0.Final > Reporter: Michal Babacek > Assignee: Radoslav Husar > Fix For: 1.3.1.Beta3 > > > While I was working on [issue 138|https://github.com/modcluster/mod_cluster/issues/138] (MODCLUSTER-448), it came to my attention that one can't force EAP 6.4 Beta (jbossweb, mod_cluster 1.2.11) to send anything like {{ajp://0.0.0.0:8009}} to the balancer. If one sets the application server to bind to 0.0.0.0, mod_cluster core correctly guesses 127.0.0.1 and sends {{ajp:/127.0.0.1:8009}} to the balancer. > On the contrary, WildFly goes only half way: it reports 127.0.0.1 in the log: > {noformat} > [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000012: default-server connector will use /127.0.0.1 > {noformat} > and yet it sends 0.0.0.0 to the balancer: > {noformat} > Node localhost (ajp://0.0.0.0:8009): > {noformat} > Note the {{localhost}} string in place of properly generated UUID: MODCLUSTER-451. > For some historical context, I suggest: MODCLUSTER-91 and MODCLUSTER-168 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-452) mod_cluster with WildFly reports 0.0.0.0 to the balancer

by Michal Babacek (JIRA)

Michal Babacek created MODCLUSTER-452: ----------------------------------------- Summary: mod_cluster with WildFly reports 0.0.0.0 to the balancer Key: MODCLUSTER-452 URL: https://issues.jboss.org/browse/MODCLUSTER-452 Project: mod_cluster Issue Type: Bug Components: Core & Container Integration (Java) Affects Versions: 1.3.0.Final Reporter: Michal Babacek Assignee: Radoslav Husar While I was working on [issue 138|https://github.com/modcluster/mod_cluster/issues/138] (MODCLUSTER-448), it came to my attention that one can't force EAP 6.4 Beta (jbossweb, mod_cluster 1.2.11) to send anything like {{ajp://0.0.0.0:8009}} to the balancer. If one sets the application server to bind to 0.0.0.0, mod_cluster core correctly guesses 127.0.0.1 and sends {{ajp:/127.0.0.1:8009}} to the balancer. On the contrary, WildFly goes only half way: it reports 127.0.0.1 in the log: {noformat} [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000012: default-server connector will use /127.0.0.1 {noformat} and yet it sends 0.0.0.0 to the balancer: {noformat} Node localhost (ajp://0.0.0.0:8009): {noformat} Note the {{localhost}} string in place of properly generated UUID: MODCLUSTER-451. For some historical context, I suggest: MODCLUSTER-91 and MODCLUSTER-168 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

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

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-448?page=com.atlassian.jira.pl... ] Michal Babacek commented on MODCLUSTER-448: ------------------------------------------- * The linked PR brings only the {{\[error\]}} message, it does not address the consequent process/thread crash. * I was able to reproduce the crash with Apache HTTP Server 2.2.26. It seems that Apache HTTP Server 2.4.6 is not vulnerable to this apr flaw. > 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 Babacek > Assignee: Michal Babacek > Fix For: 1.3.1.Beta3 > > > 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.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-451) UUID for auto-generated jvmRoute does not work with WildFly

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-451?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-451: ------------------------------------------- We no longer use it in WildFly, instance-id must be set uniquely on all nodes. Also note you should never bind to 0.0.0.0. > UUID for auto-generated jvmRoute does not work with WildFly > ----------------------------------------------------------- > > Key: MODCLUSTER-451 > URL: https://issues.jboss.org/browse/MODCLUSTER-451 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.0.Final > Environment: WildFly 8.2.0.Final, mod_cluster 1.3.0 > Reporter: Michal Babacek > Assignee: Radoslav Husar > Fix For: 1.3.1.Beta3 > > > It appears that UUID is not generated with WildFly/Undertow/mod_cluster setup. For example, if one does not set any instance-id/jvmRoute and binds to 0.0.0.0, one gets {{localhost}} jvmRoute Instead of a proper UUID. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-451) UUID for auto-generated jvmRoute does not work with WildFly

by Michal Babacek (JIRA)

Michal Babacek created MODCLUSTER-451: ----------------------------------------- Summary: UUID for auto-generated jvmRoute does not work with WildFly Key: MODCLUSTER-451 URL: https://issues.jboss.org/browse/MODCLUSTER-451 Project: mod_cluster Issue Type: Bug Components: Core & Container Integration (Java) Affects Versions: 1.3.0.Final Environment: WildFly 8.2.0.Final, mod_cluster 1.3.0 Reporter: Michal Babacek Assignee: Radoslav Husar Fix For: 1.3.1.Beta3 It appears that UUID is not generated with WildFly/Undertow/mod_cluster setup. For example, if one does not set any instance-id/jvmRoute and binds to 0.0.0.0, one gets {{localhost}} jvmRoute Instead of a proper UUID. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

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

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-448?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-448: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/140 > 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 Babacek > Assignee: Michal Babacek > Fix For: 1.3.1.Beta3 > > > 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.3.11#6341)

9 years, 10 months

1
0
0 / 0

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

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-448?page=com.atlassian.jira.pl... ] Michal Babacek reassigned MODCLUSTER-448: ----------------------------------------- Assignee: Michal Babacek (was: Jean-Frederic Clere) > 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 Babacek > Assignee: Michal Babacek > Fix For: 1.3.1.Beta3 > > > 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.3.11#6341)

9 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 February 2015