July 2016 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-530) Add a disabled-contexts feature for mod_cluster

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-530?page=com.atlassian.jira.pl... ] Work on MODCLUSTER-530 started by Radoslav Husar. ------------------------------------------------- > Add a disabled-contexts feature for mod_cluster > ----------------------------------------------- > > Key: MODCLUSTER-530 > URL: https://issues.jboss.org/browse/MODCLUSTER-530 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Affects Versions: 1.3.3.Final > Reporter: Aaron Ogburn > Assignee: Radoslav Husar > > Currently, if you want contexts disabled at start up, you can only have them all disabled with auto-enable-contexts="false". In some cases, you may want only specific apps disabled at start up. So it would be helpful to have a disabled-contexts parameter. This would accept a list of contexts similar to excluded-contexts, but the listed contexts in disabled-contexts would designate what contexts must be added to the balancer in a disabled state. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-528) Re-think catalina/tomcat dependencies so as it is possible to build without tomcat7 API

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-528?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-528: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/211 Opened PR https://github.com/modcluster/mod_cluster/pull/211 but I am reluctant. > Re-think catalina/tomcat dependencies so as it is possible to build without tomcat7 API > --------------------------------------------------------------------------------------- > > Key: MODCLUSTER-528 > URL: https://issues.jboss.org/browse/MODCLUSTER-528 > Project: mod_cluster > Issue Type: Enhancement > Affects Versions: 1.3.3.Final > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > It is not possible (or I'm doing something wrong) to build mod_cluster Tomcat libs with Tomcat 8-only API. > I hit this problem with RPM build on Fedora where I cannot download random stuff from maven central and I need to specify dependencies beforehand. > h3. Description > * container/catalina contains calls to API that is deprecated in Tomcat 7 and missing in Tomcat 8, so I have to apply this patch: [MODCLUSTER-528-CatalinaContext.java.patch|https://github.com/Karm/mod_clu...] before build > * profiles and test dependencies and Servlet API dependencies needs hacks to build without Tomcat 7 too: see other patches in [mod_cluster-fedora-packages/|https://github.com/Karm/mod_cluster-fedora-p...] > h3. Suggestion > * architecture dependencies so as it is possible to build mod_cluster with Tomcat 8 API only (and Tomcat 7 API only) > * drop Tomcat 6 and JBossWeb from 1.3.x as they are not used in 1.3.x anyway (last use of Tomcat 6 and JBossWeb is 1.2.x) > h3. Fedora 24 offers only Tomcat 8 > ...so does it even make sense to offer users Tomcat 7 libs RPM? At the moment, I have it disabled. Note: Former mod_cluster RPM (1.2.6) hasn't been distributing any usable tomcat integration; it has been AS7/JBossWeb one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-528) Re-think catalina/tomcat dependencies so as it is possible to build without tomcat7 API

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-528?page=com.atlassian.jira.pl... ] Radoslav Husar edited comment on MODCLUSTER-528 at 7/29/16 11:33 AM: --------------------------------------------------------------------- This was already dicsussed. Unfortunately there is not much more that could be done here apart from patching. To build the base (called tomcat module based on tomcat7 in master) withouth tomcat7 dependencies, the patch would "unimplement" the methods (throw MethodNotImplementedException) and remove the imports and in runtime, these methods are overriden. To build master with tomcat8 dependencies just apply this patch and use -PTC8. Note that this wont work with tomcat85 nor tomcat9. {noformat} diff --git a/container/tomcat/pom.xml b/container/tomcat/pom.xml index 0fcc914..1abce26 100644 --- a/container/tomcat/pom.xml +++ b/container/tomcat/pom.xml @@ -48,7 +48,6 @@ </dependency> </dependencies> <profiles> -  <profile> <id>TC7</id> <activation> {noformat} Maybe the patch enabling build for tomcat8 could be merged upstream, but its not a real solution as it wont work beyond that version. was (Author: rhusar): This was already dicsussed. Unfortunately there is not much more that could be done here apart from patching. To build the base (called tomcat module based on tomcat7 in master) withouth tomcat7 dependencies, the patch would "unimplement" the methods (throw MethodNotImplementedException) and remove the imports and in runtime, these methods are overriden. To build master with tomcat8 dependencies just apply this patch and use -PTC8. Note that this wont work with tomcat85 nor tomcat9. {noformat} diff --git a/container/tomcat/pom.xml b/container/tomcat/pom.xml index 0fcc914..1abce26 100644 --- a/container/tomcat/pom.xml +++ b/container/tomcat/pom.xml @@ -48,7 +48,6 @@ </dependency> </dependencies> <profiles> -  <profile> <id>TC7</id> <activation> {noformat} > Re-think catalina/tomcat dependencies so as it is possible to build without tomcat7 API > --------------------------------------------------------------------------------------- > > Key: MODCLUSTER-528 > URL: https://issues.jboss.org/browse/MODCLUSTER-528 > Project: mod_cluster > Issue Type: Enhancement > Affects Versions: 1.3.3.Final > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > It is not possible (or I'm doing something wrong) to build mod_cluster Tomcat libs with Tomcat 8-only API. > I hit this problem with RPM build on Fedora where I cannot download random stuff from maven central and I need to specify dependencies beforehand. > h3. Description > * container/catalina contains calls to API that is deprecated in Tomcat 7 and missing in Tomcat 8, so I have to apply this patch: [MODCLUSTER-528-CatalinaContext.java.patch|https://github.com/Karm/mod_clu...] before build > * profiles and test dependencies and Servlet API dependencies needs hacks to build without Tomcat 7 too: see other patches in [mod_cluster-fedora-packages/|https://github.com/Karm/mod_cluster-fedora-p...] > h3. Suggestion > * architecture dependencies so as it is possible to build mod_cluster with Tomcat 8 API only (and Tomcat 7 API only) > * drop Tomcat 6 and JBossWeb from 1.3.x as they are not used in 1.3.x anyway (last use of Tomcat 6 and JBossWeb is 1.2.x) > h3. Fedora 24 offers only Tomcat 8 > ...so does it even make sense to offer users Tomcat 7 libs RPM? At the moment, I have it disabled. Note: Former mod_cluster RPM (1.2.6) hasn't been distributing any usable tomcat integration; it has been AS7/JBossWeb one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-528) Re-think catalina/tomcat dependencies so as it is possible to build without tomcat7 API

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-528?page=com.atlassian.jira.pl... ] Radoslav Husar edited comment on MODCLUSTER-528 at 7/29/16 11:30 AM: --------------------------------------------------------------------- This was already dicsussed. Unfortunately there is not much more that could be done here apart from patching. To build the base (called tomcat module based on tomcat7 in master) withouth tomcat7 dependencies, the patch would "unimplement" the methods (throw MethodNotImplementedException) and remove the imports and in runtime, these methods are overriden. To build master with tomcat8 dependencies just apply this patch and use -PTC8. Note that this wont work with tomcat85 nor tomcat9. {noformat} diff --git a/container/tomcat/pom.xml b/container/tomcat/pom.xml index 0fcc914..1abce26 100644 --- a/container/tomcat/pom.xml +++ b/container/tomcat/pom.xml @@ -48,7 +48,6 @@ </dependency> </dependencies> <profiles> -  <profile> <id>TC7</id> <activation> {noformat} was (Author: rhusar): Unfortunately there is not much more that could be done here apart from patching. To build the base (called tomcat module based on tomcat7 in master) withouth tomcat7 dependencies, the patch would "unimplement" the methods (throw MethodNotImplementedException) and remove the imports and in runtime, these methods are overriden. To build master with tomcat8 dependencies just apply this patch and use -PTC8. {noformat} diff --git a/container/tomcat/pom.xml b/container/tomcat/pom.xml index 0fcc914..1abce26 100644 --- a/container/tomcat/pom.xml +++ b/container/tomcat/pom.xml @@ -48,7 +48,6 @@ </dependency> </dependencies> <profiles> -  <profile> <id>TC7</id> <activation> {noformat} > Re-think catalina/tomcat dependencies so as it is possible to build without tomcat7 API > --------------------------------------------------------------------------------------- > > Key: MODCLUSTER-528 > URL: https://issues.jboss.org/browse/MODCLUSTER-528 > Project: mod_cluster > Issue Type: Enhancement > Affects Versions: 1.3.3.Final > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > It is not possible (or I'm doing something wrong) to build mod_cluster Tomcat libs with Tomcat 8-only API. > I hit this problem with RPM build on Fedora where I cannot download random stuff from maven central and I need to specify dependencies beforehand. > h3. Description > * container/catalina contains calls to API that is deprecated in Tomcat 7 and missing in Tomcat 8, so I have to apply this patch: [MODCLUSTER-528-CatalinaContext.java.patch|https://github.com/Karm/mod_clu...] before build > * profiles and test dependencies and Servlet API dependencies needs hacks to build without Tomcat 7 too: see other patches in [mod_cluster-fedora-packages/|https://github.com/Karm/mod_cluster-fedora-p...] > h3. Suggestion > * architecture dependencies so as it is possible to build mod_cluster with Tomcat 8 API only (and Tomcat 7 API only) > * drop Tomcat 6 and JBossWeb from 1.3.x as they are not used in 1.3.x anyway (last use of Tomcat 6 and JBossWeb is 1.2.x) > h3. Fedora 24 offers only Tomcat 8 > ...so does it even make sense to offer users Tomcat 7 libs RPM? At the moment, I have it disabled. Note: Former mod_cluster RPM (1.2.6) hasn't been distributing any usable tomcat integration; it has been AS7/JBossWeb one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-528) Re-think catalina/tomcat dependencies so as it is possible to build without tomcat7 API

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-528?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-528: ------------------------------------------- Unfortunately there is not much more that could be done here apart from patching. To build the base (called tomcat module based on tomcat7 in master) withouth tomcat7 dependencies, the patch would "unimplement" the methods (throw MethodNotImplementedException) and remove the imports and in runtime, these methods are overriden. To build master with tomcat8 dependencies just apply this patch and use -PTC8. {noformat} diff --git a/container/tomcat/pom.xml b/container/tomcat/pom.xml index 0fcc914..1abce26 100644 --- a/container/tomcat/pom.xml +++ b/container/tomcat/pom.xml @@ -48,7 +48,6 @@ </dependency> </dependencies> <profiles> -  <profile> <id>TC7</id> <activation> {noformat} > Re-think catalina/tomcat dependencies so as it is possible to build without tomcat7 API > --------------------------------------------------------------------------------------- > > Key: MODCLUSTER-528 > URL: https://issues.jboss.org/browse/MODCLUSTER-528 > Project: mod_cluster > Issue Type: Enhancement > Affects Versions: 1.3.3.Final > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > It is not possible (or I'm doing something wrong) to build mod_cluster Tomcat libs with Tomcat 8-only API. > I hit this problem with RPM build on Fedora where I cannot download random stuff from maven central and I need to specify dependencies beforehand. > h3. Description > * container/catalina contains calls to API that is deprecated in Tomcat 7 and missing in Tomcat 8, so I have to apply this patch: [MODCLUSTER-528-CatalinaContext.java.patch|https://github.com/Karm/mod_clu...] before build > * profiles and test dependencies and Servlet API dependencies needs hacks to build without Tomcat 7 too: see other patches in [mod_cluster-fedora-packages/|https://github.com/Karm/mod_cluster-fedora-p...] > h3. Suggestion > * architecture dependencies so as it is possible to build mod_cluster with Tomcat 8 API only (and Tomcat 7 API only) > * drop Tomcat 6 and JBossWeb from 1.3.x as they are not used in 1.3.x anyway (last use of Tomcat 6 and JBossWeb is 1.2.x) > h3. Fedora 24 offers only Tomcat 8 > ...so does it even make sense to offer users Tomcat 7 libs RPM? At the moment, I have it disabled. Note: Former mod_cluster RPM (1.2.6) hasn't been distributing any usable tomcat integration; it has been AS7/JBossWeb one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 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: -------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Labels: tomcat (was: ) > 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: 2.0.0.Alpha1, 1.3.4.Final > > > 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 (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-397) StickySessions don't work for ProxyPass from unenabled context

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on MODCLUSTER-397: ---------------------------------------------------- Michal Karm Babacek <mbabacek(a)redhat.com> changed the Status of [bug 1338641|https://bugzilla.redhat.com/show_bug.cgi?id=1338641] from NEW to ON_QA > StickySessions don't work for ProxyPass from unenabled context > -------------------------------------------------------------- > > Key: MODCLUSTER-397 > URL: https://issues.jboss.org/browse/MODCLUSTER-397 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Michal Karm Babacek > Fix For: 1.3.3.Final, 2.0.0.Alpha1, 1.2.13.Final > > > Sticky sessions are not maintained if you try to ProxyPass from an unenabled context to an enabled one. For example, consider JBoss with just /foo deployed and enabled via MCMP. Then try to ProxyPass / to /foo/ on httpd: > CreateBalancers 1 > ... > ProxyPass / balancer://mycluster/foo/ stickysession=JSESSIONID|jsessionid nofailover=On -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-397) StickySessions don't work for ProxyPass from unenabled context

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on MODCLUSTER-397: ---------------------------------------------------- Michal Karm Babacek <mbabacek(a)redhat.com> changed the Status of [bug 1085427|https://bugzilla.redhat.com/show_bug.cgi?id=1085427] from NEW to ON_QA > StickySessions don't work for ProxyPass from unenabled context > -------------------------------------------------------------- > > Key: MODCLUSTER-397 > URL: https://issues.jboss.org/browse/MODCLUSTER-397 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Michal Karm Babacek > Fix For: 1.3.3.Final, 2.0.0.Alpha1, 1.2.13.Final > > > Sticky sessions are not maintained if you try to ProxyPass from an unenabled context to an enabled one. For example, consider JBoss with just /foo deployed and enabled via MCMP. Then try to ProxyPass / to /foo/ on httpd: > CreateBalancers 1 > ... > ProxyPass / balancer://mycluster/foo/ stickysession=JSESSIONID|jsessionid nofailover=On -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 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 commented on MODCLUSTER-529: ------------------------------------------- Fix in tomcat upstream, see https://github.com/apache/tomcat/pull/33 > 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 > Fix For: 2.0.0.Alpha1, 1.3.4.Final > > > 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 (v6.4.11#64026)

8 years, 4 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 commented on MODCLUSTER-529: ------------------------------------------- Problem in 1.3.x is just wrong class name. > 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 > Fix For: 2.0.0.Alpha1, 1.3.4.Final > > > 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 (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues July 2016