August 2017 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-485) Move CI to Travis

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-485?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-485: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Move CI to Travis > ----------------- > > Key: MODCLUSTER-485 > URL: https://issues.jboss.org/browse/MODCLUSTER-485 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: CI > Fix For: 1.3.4.Final, 1.4.0.Alpha1, 2.0.0.Alpha1 > > > -I ran into this while adding support for Tomcat 9.- > -What the CI should be testing, give the number of JDKs and different container versions that we support, we should build with respective jdks and versions:- > -jdk6 + mvn verify -PTC6- > -jdk7 + mvn verify -PTC7- > -jdk7 + mvn verify -PAS7- > -jdk8 + mvn verify -PTC8- > -jdk7/8 + mvn verify- > The situation has changed since original proposal fixing CI with proper dependencies for tomcat versions. Taking into account support for legacy containers has been dropped in master, so now we have desired combinations: > * jdk7 + jdk8 and default profile (excludes Tomcat 9) -> 3 combos on travis > * jdk 8 + Tomcat 9 profile -> 1 combo on travis > See http://tomcat.apache.org/whichversion.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-485) Move CI to Travis

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-485?page=com.atlassian.jira.pl... ] Radoslav Husar reopened MODCLUSTER-485: --------------------------------------- > Move CI to Travis > ----------------- > > Key: MODCLUSTER-485 > URL: https://issues.jboss.org/browse/MODCLUSTER-485 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: CI > Fix For: 1.3.4.Final, 1.4.0.Alpha1, 2.0.0.Alpha1 > > > -I ran into this while adding support for Tomcat 9.- > -What the CI should be testing, give the number of JDKs and different container versions that we support, we should build with respective jdks and versions:- > -jdk6 + mvn verify -PTC6- > -jdk7 + mvn verify -PTC7- > -jdk7 + mvn verify -PAS7- > -jdk8 + mvn verify -PTC8- > -jdk7/8 + mvn verify- > The situation has changed since original proposal fixing CI with proper dependencies for tomcat versions. Taking into account support for legacy containers has been dropped in master, so now we have desired combinations: > * jdk7 + jdk8 and default profile (excludes Tomcat 9) -> 3 combos on travis > * jdk 8 + Tomcat 9 profile -> 1 combo on travis > See http://tomcat.apache.org/whichversion.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-482) Drop Tomcat 6 and JBoss Web support

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-482?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-482: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Drop Tomcat 6 and JBoss Web support > ----------------------------------- > > Key: MODCLUSTER-482 > URL: https://issues.jboss.org/browse/MODCLUSTER-482 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.4.0.Alpha1, 2.0.0.Alpha1 > > > See https://tomcat.apache.org/tomcat-60-eol.html > The reason why this is interesting is that we can have more common code and simplify the how the container support modules are structured. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-480) Tomcat 8 Context#isDistributable implementation needs to consult the underlying context instead of the manager

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-480?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-480: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Tomcat 8 Context#isDistributable implementation needs to consult the underlying context instead of the manager > -------------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-480 > URL: https://issues.jboss.org/browse/MODCLUSTER-480 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.2.Final, 1.4.0.Alpha1, 2.0.0.Alpha1 > > > https://tomcat.apache.org/tomcat-8.0-doc/api/org/apache/catalina/Manager.... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-479) Add support for Tomcat 9

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-479?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-479: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Add support for Tomcat 9 > ------------------------ > > Key: MODCLUSTER-479 > URL: https://issues.jboss.org/browse/MODCLUSTER-479 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.4.0.Alpha1, 2.0.0.Alpha1 > > > This won't be binary compatible with Tomcat 8 classes because there are some differences. > Comet support has bee removed, see https://github.com/apache/tomcat/commit/376a308dbb1742f9fc88e693fb8100c44... > Service.getContainer refactored https://github.com/apache/tomcat/commit/2d9d4519cea1879209848952832fe194a... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-529) MBeans descriptions are not loaded in JMX for ModClusterListener

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-529?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-529: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > MBeans descriptions are not loaded in JMX for ModClusterListener > ---------------------------------------------------------------- > > Key: MODCLUSTER-529 > URL: https://issues.jboss.org/browse/MODCLUSTER-529 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.3.Final, 2.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Labels: tomcat > Fix For: 1.3.4.Final, 1.4.0.Alpha1, 2.0.0.Alpha1 > > > Several problems: > # we need to support org.jboss.modcluster.container.tomcat.ModClusterListener and org.jboss.modcluster.container.catalina.standalone.ModClusterListener at the same time > # name of the beans-destriptors file is now wrong, since i followed the description at https://tomcat.apache.org/tomcat-7.0-doc/mbeans-descriptor-howto.html which is totally incorrect, those resources are not loaded! (PR to Apache shortly) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-574) Allow custom LoadMetric implementations to put node into error state (load of -1)

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-574?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-574: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Allow custom LoadMetric implementations to put node into error state (load of -1) > --------------------------------------------------------------------------------- > > Key: MODCLUSTER-574 > URL: https://issues.jboss.org/browse/MODCLUSTER-574 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Affects Versions: 1.3.6.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 1.4.0.Alpha1, 2.0.0.Alpha1 > > > This allows implementors of custom load metrics to put the node temporarily in the error state, e.g. when a connection to some sort of backend service is unavailable. > This has been requested multiple times, last time https://github.com/modcluster/mod_cluster/issues/244 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-566) Exclusion list cannot be pre-populated in init()

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-566?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-566: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Exclusion list cannot be pre-populated in init() > ------------------------------------------------ > > Key: MODCLUSTER-566 > URL: https://issues.jboss.org/browse/MODCLUSTER-566 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.6.CR1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 1.3.6.CR2, 1.4.0.Alpha1, 2.0.0.Alpha1 > > > The exclusion list is unnecessarily populated eagerly on init(). This does not work in container such as WildFly where services are started asynchronously and virtual hosts and contexts can be added at any time. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-509) Excluded contexts which are not specific to a host should be excluded on all hosts

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-509?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-509: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Excluded contexts which are not specific to a host should be excluded on all hosts > ---------------------------------------------------------------------------------- > > Key: MODCLUSTER-509 > URL: https://issues.jboss.org/browse/MODCLUSTER-509 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.3.2.Final, 1.2.12.Final, 2.0.0.Alpha1 > Environment: Tomcat8 (haven't tried elsewhere yet); mod_cluster version 2.0.0.Alpha1-SNAPSHOT > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Priority: Critical > Fix For: 1.3.3.Final, 1.2.13.Final, 1.4.0.Alpha1, 2.0.0.Alpha1 > > > With the following configuration: > {code} > <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" > loadMetricClass="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric" > loadMetricCapacity="1" > loadHistory="9" > loadDecayFactor="2" > stickySession="true" > stickySessionForce="false" > stickySessionRemove="true" > advertise="true" > advertiseGroupAddress="224.0.1.105" > advertisePort="23364" > advertiseInterface="10.40.4.50" > excludedContexts="ROOT,docs,manager,host-manager,examples" > /> > {code} > And these contexts in webapps: > {code} > clusterbench docs examples host-manager manager ROOT > {code} > One expects this output on Mod_cluster manger console: > {code} > Virtual Host 1: > Contexts: > /clusterbench, Status: ENABLED Request: 0 Disable Stop > Aliases: > localhost > {code} > It works, unless you configure additional VirtualHosts: > {code} > <Host name="LOCALHOST" appBase="webapps" unpackWARs="true" autoDeploy="true"> > <Alias>LOCALHOST</Alias> > <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" > prefix="localhost_access_log" suffix=".txt" > pattern="%h %l %u %t "%r" %s %b" /> > </Host> > <Host name="KARM.BRQ.REDHAT.COM" appBase="webapps" unpackWARs="true" autoDeploy="true"> > <Alias>KARM.BRQ.REDHAT.COM</Alias> > <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" > prefix="localhost_access_log" suffix=".txt" > pattern="%h %l %u %t "%r" %s %b" /> > </Host> > {code} > result: > {code} > Node worker1 (ajp://10.40.4.50:8009): > Enable Contexts Disable Contexts Stop Contexts > Balancer: mycluster,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 1,Ttl: 60000000,Status: OK,Elected: 0,Read: 0,Transferred: 0,Connected: 0,Load: 100 > Virtual Host 2: > Contexts: > /docs, Status: ENABLED Request: 0 Disable Stop > /manager, Status: ENABLED Request: 0 Disable Stop > /host-manager, Status: ENABLED Request: 0 Disable Stop > /examples, Status: ENABLED Request: 0 Disable Stop > /, Status: ENABLED Request: 0 Disable Stop > /clusterbench, Status: ENABLED Request: 0 Disable Stop > Aliases: > karm.brq.redhat.com > Virtual Host 1: > Contexts: > /clusterbench, Status: ENABLED Request: 0 Disable Stop > Aliases: > localhost > {code} > I find this bug being of Critical priority, because it could coax users into believing they excluded certain context while in fact they didn't. > WDYT? Is it possible to tweak with the Listener's configuration somehow? > THX. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-518) Support JDK9 build 9-ea (June 2016)

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-518?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-518: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Support JDK9 build 9-ea (June 2016) > ----------------------------------- > > Key: MODCLUSTER-518 > URL: https://issues.jboss.org/browse/MODCLUSTER-518 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Labels: jdk9 > Fix For: 1.4.0.Alpha1, 2.0.0.Alpha1 > > > JDK 9 Early Access Downloads available https://jdk9.java.net/download/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 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 August 2017