May 2015 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-415) Drop support for HP-UX older than HP-UX 11v3 (Itanium 64)

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-415?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-415: -------------------------------------- Fix Version/s: 1.3.2.Alpha1 (was: 1.3.1.Final) > Drop support for HP-UX older than HP-UX 11v3 (Itanium 64) > --------------------------------------------------------- > > Key: MODCLUSTER-415 > URL: https://issues.jboss.org/browse/MODCLUSTER-415 > Project: mod_cluster > Issue Type: Feature Request > Components: Documentation & Demos, Native (httpd modules) > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > Fix For: 1.3.2.Alpha1 > > > As per https://access.redhat.com/site/articles/111663 we can drop support for HP-UX older than HP-UX 11v3 (Itanium 64). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-429) Some problems were encountered while building the effective model for org.jboss:User-Guide-en:jdocbook:1.3.1.Alpha3-SNAPSHOT

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-429?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-429: -------------------------------------- Fix Version/s: 1.3.2.Alpha1 (was: 1.3.1.Final) > Some problems were encountered while building the effective model for org.jboss:User-Guide-en:jdocbook:1.3.1.Alpha3-SNAPSHOT > ---------------------------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-429 > URL: https://issues.jboss.org/browse/MODCLUSTER-429 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 1.3.2.Alpha1 > > > [WARNING] > [WARNING] Some problems were encountered while building the effective model for org.jboss:User-Guide-en:jdocbook:1.3.1.Alpha3-SNAPSHOT > [WARNING] 'artifactId' contains an expression but should be a constant. @ org.jboss:User-Guide-${translation}:1.3.1.Alpha3-SNAPSHOT, /home/rhusar/git/mod_cluster/docs/userguide/pom.xml, line 31, column 17 > [WARNING] 'parent.relativePath' points at org.jboss.mod_cluster:org.jboss.mod_cluster-docs instead of org.jboss:jboss-parent, please verify your project structure @ org.jboss:User-Guide-${translation}:1.3.1.Alpha3-SNAPSHOT, /home/rhusar/git/mod_cluster/docs/userguide/pom.xml, line 24, column 13 > [WARNING] > [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. > [WARNING] > [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. > [WARNING] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

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

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-430?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-430: -------------------------------------- Fix Version/s: 1.3.2.Alpha1 (was: 1.3.1.Final) > 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 Babacek > Fix For: 1.2.11.Final, 1.3.2.Alpha1 > > > 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 (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-440) Release 1.3.x binaries to mod-cluster.jboss.org/downloads

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-440?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-440: -------------------------------------- Fix Version/s: 1.3.2.Alpha1 (was: 1.3.1.Final) > Release 1.3.x binaries to mod-cluster.jboss.org/downloads > --------------------------------------------------------- > > Key: MODCLUSTER-440 > URL: https://issues.jboss.org/browse/MODCLUSTER-440 > Project: mod_cluster > Issue Type: Task > Components: Documentation & Demos > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > Fix For: 1.3.2.Alpha1 > > > We should really do this and at least we should release the JARs so people get Tomcat 8 support. People using AS7 or WildFly get their modcluster jars out of box. > ..and blog/tweet about it :-) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-439) Installation for Tomcat 6/7/8 is cumbersome, revamp distribution profile

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-439?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-439: -------------------------------------- Fix Version/s: 1.3.2.Alpha1 (was: 1.3.1.Final) > Installation for Tomcat 6/7/8 is cumbersome, revamp distribution profile > ------------------------------------------------------------------------ > > Key: MODCLUSTER-439 > URL: https://issues.jboss.org/browse/MODCLUSTER-439 > Project: mod_cluster > Issue Type: Feature Request > Components: Documentation & Demos > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: tomcat > Fix For: 1.3.2.Alpha1 > > > The installation in the docs now expects to go around and copy lots of jars to the /lib dir, the package we ship has all the tomcat 6 and 7 jars in the same spot... we shoud align this to be easier and/or include a readme file in the directory. Also update the documentation for people bulding from source. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-450) Reenable testMulticastSocketNoCrossTalk test

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-450?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-450: -------------------------------------- Fix Version/s: 1.3.2.Alpha1 (was: 1.3.1.Final) > Reenable testMulticastSocketNoCrossTalk test > -------------------------------------------- > > Key: MODCLUSTER-450 > URL: https://issues.jboss.org/browse/MODCLUSTER-450 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.3.1.Beta2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.2.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 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: -------------------------------------- Fix Version/s: 1.3.2.Alpha1 (was: 1.3.1.Final) > 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.2.Alpha1 > > > 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.15#6346)

8 years, 11 months

1
0
0 / 0

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

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-448?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-448: -------------------------------------- Fix Version/s: 1.3.2.Alpha1 (was: 1.3.1.Final) > 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.2.Alpha1 > > > 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.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-449) Implement ramp-up when starting new nodes

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-449?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-449: -------------------------------------- Fix Version/s: 1.3.2.Alpha1 (was: 1.3.1.Final) > Implement ramp-up when starting new nodes > ----------------------------------------- > > Key: MODCLUSTER-449 > URL: https://issues.jboss.org/browse/MODCLUSTER-449 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 1.3.2.Alpha1 > > > IIUC this has been a problem since inception. The problem is that the initial load stays in effect for performing load-balancing decisions until a new stat interval kicks in. > This effect is mitigated by load decay over time, but for the time a new node joins in, it can get overloaded upon startup. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-456) Upgrade build to JDK 7

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-456?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-456: -------------------------------------- Fix Version/s: 1.3.2.Alpha1 (was: 1.3.1.Final) > Upgrade build to JDK 7 > ---------------------- > > Key: MODCLUSTER-456 > URL: https://issues.jboss.org/browse/MODCLUSTER-456 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.2.Alpha1 > > > {code}[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project mod_cluster-core: Compilation failure > [INFO] [ERROR] /home/rhusar/git/mod_cluster/core/src/main/java/org/jboss/modcluster/config/impl/ModClusterConfig.java:[88,43] getHostString() is not public in java.net.InetSocketAddress; cannot be accessed from outside package > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues May 2015