June 2017 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-602) Remove jboss-logging from mod_cluster code that runs on Tomcat

by Coty Sutherland (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-602?page=com.atlassian.jira.pl... ] Coty Sutherland reopened MODCLUSTER-602: ---------------------------------------- You don't think the mod_cluster module should use what's native to the container? Tomcat doesn't log via jboss-logging, it uses JULI. So it doesn't help that mod_cluster _inside_ Tomcat uses jboss-logging for it's few messages; IMO it's a dependency that we have to keep for a handful of messages that could be logged with the containers logging framework. Using jboss-logging in EAP and Wildfly is fine, but JULI is Tomcat's native logging framework so it'd be nice if we could use that to log rather than jboss-logging. > Remove jboss-logging from mod_cluster code that runs on Tomcat > -------------------------------------------------------------- > > Key: MODCLUSTER-602 > URL: https://issues.jboss.org/browse/MODCLUSTER-602 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Reporter: Coty Sutherland > Assignee: Radoslav Husar > > I'm trying to get rid of all of the JBoss dependencies that I can from Tomcat in JWS and found that jboss-logging is used by mod_cluster. Is it possible to remove jboss-logging from the mod_cluster code that runs on Tomcat and use JULI or some other framework? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-603) https://ci.modcluster.io windows httpd: mod_proxy_cluster for Apache Lounge

by Michal Karm Babacek (JIRA)

Michal Karm Babacek created MODCLUSTER-603: ---------------------------------------------- Summary: https://ci.modcluster.io windows httpd: mod_proxy_cluster for Apache Lounge Key: MODCLUSTER-603 URL: https://issues.jboss.org/browse/MODCLUSTER-603 Project: mod_cluster Issue Type: Bug Components: CI & Packaging Reporter: Michal Karm Babacek Assignee: Michal Karm Babacek mod_proxy_cluster regular CI for users of http://apachelounge.com/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-420) Drop support for httpd older than 2.4

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-420?page=com.atlassian.jira.pl... ] Work on MODCLUSTER-420 stopped by Radoslav Husar. ------------------------------------------------- > Drop support for httpd older than 2.4 > ------------------------------------- > > Key: MODCLUSTER-420 > URL: https://issues.jboss.org/browse/MODCLUSTER-420 > Project: mod_cluster > Issue Type: Task > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 2.0.0.Alpha1 > > > The EWS is built on 2.2.24 and further on when productizing modcluster, this version might even increase. Lets consider dropping older versions prior to this one. > If the decision is made, you can assign to me to remove the support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-602) Remove jboss-logging from mod_cluster code that runs on Tomcat

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-602?page=com.atlassian.jira.pl... ] Radoslav Husar closed MODCLUSTER-602. ------------------------------------- Resolution: Rejected This came as a business requirement via ANDIAMO-2 requiring us to standardize jboss-logging. I am rejecting for now unless there are compelling reasons for the change. > Remove jboss-logging from mod_cluster code that runs on Tomcat > -------------------------------------------------------------- > > Key: MODCLUSTER-602 > URL: https://issues.jboss.org/browse/MODCLUSTER-602 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Reporter: Coty Sutherland > Assignee: Radoslav Husar > > I'm trying to get rid of all of the JBoss dependencies that I can from Tomcat in JWS and found that jboss-logging is used by mod_cluster. Is it possible to remove jboss-logging from the mod_cluster code that runs on Tomcat and use JULI or some other framework? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-602) Remove jboss-logging from mod_cluster code that runs on Tomcat

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-602?page=com.atlassian.jira.pl... ] Radoslav Husar reassigned MODCLUSTER-602: ----------------------------------------- Assignee: Radoslav Husar (was: Jean-Frederic Clere) > Remove jboss-logging from mod_cluster code that runs on Tomcat > -------------------------------------------------------------- > > Key: MODCLUSTER-602 > URL: https://issues.jboss.org/browse/MODCLUSTER-602 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Reporter: Coty Sutherland > Assignee: Radoslav Husar > > I'm trying to get rid of all of the JBoss dependencies that I can from Tomcat in JWS and found that jboss-logging is used by mod_cluster. Is it possible to remove jboss-logging from the mod_cluster code that runs on Tomcat and use JULI or some other framework? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-602) Remove jboss-logging from mod_cluster code that runs on Tomcat

by Coty Sutherland (JIRA)

Coty Sutherland created MODCLUSTER-602: ------------------------------------------ Summary: Remove jboss-logging from mod_cluster code that runs on Tomcat Key: MODCLUSTER-602 URL: https://issues.jboss.org/browse/MODCLUSTER-602 Project: mod_cluster Issue Type: Bug Components: Core & Container Integration (Java) Reporter: Coty Sutherland Assignee: Jean-Frederic Clere I'm trying to get rid of all of the JBoss dependencies that I can from Tomcat in JWS and found that jboss-logging is used by mod_cluster. Is it possible to remove jboss-logging from the mod_cluster code that runs on Tomcat and use JULI or some other framework? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-600) Default session draining strategy should perform draining if last cluster member is leaving

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-600?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-600: -------------------------------------- Priority: Major (was: Critical) > Default session draining strategy should perform draining if last cluster member is leaving > ------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-600 > URL: https://issues.jboss.org/browse/MODCLUSTER-600 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.7.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Currently, the default session draining strategy consults implementation of org.jboss.modcluster.container.Context#isDistributable for whether session draining is enabled org.jboss.modcluster.config.impl.SessionDrainingStrategyEnum#isEnabled. In fact the method consulted should be checking for whether data is available on other nodes; since if the last member is leaving a data loss will occur. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-601) Default session draining strategy should perform draining if last cluster member is leaving

by Radoslav Husar (JIRA)

Radoslav Husar created MODCLUSTER-601: ----------------------------------------- Summary: Default session draining strategy should perform draining if last cluster member is leaving Key: MODCLUSTER-601 URL: https://issues.jboss.org/browse/MODCLUSTER-601 Project: mod_cluster Issue Type: Bug Components: Core & Container Integration (Java) Affects Versions: 1.3.7.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Critical Currently, the default session draining strategy consults implementation of org.jboss.modcluster.container.Context#isDistributable for whether session draining is enabled org.jboss.modcluster.config.impl.SessionDrainingStrategyEnum#isEnabled. In fact the method consulted should be checking for whether data is available on other nodes; since if the last member is leaving a data loss will occur. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-600) Default session draining strategy should perform draining if last cluster member is leaving

by Radoslav Husar (JIRA)

Radoslav Husar created MODCLUSTER-600: ----------------------------------------- Summary: Default session draining strategy should perform draining if last cluster member is leaving Key: MODCLUSTER-600 URL: https://issues.jboss.org/browse/MODCLUSTER-600 Project: mod_cluster Issue Type: Bug Components: Core & Container Integration (Java) Affects Versions: 1.3.7.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Currently, the default session draining strategy consults implementation of org.jboss.modcluster.container.Context#isDistributable for whether session draining is enabled org.jboss.modcluster.config.impl.SessionDrainingStrategyEnum#isEnabled. In fact the method consulted should be checking for whether data is available on other nodes; since if the last member is leaving a data loss will occur. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-600) Default session draining strategy should perform draining if last cluster member is leaving

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-600?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-600: -------------------------------------- Priority: Critical (was: Major) > Default session draining strategy should perform draining if last cluster member is leaving > ------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-600 > URL: https://issues.jboss.org/browse/MODCLUSTER-600 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.7.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > Currently, the default session draining strategy consults implementation of org.jboss.modcluster.container.Context#isDistributable for whether session draining is enabled org.jboss.modcluster.config.impl.SessionDrainingStrategyEnum#isEnabled. In fact the method consulted should be checking for whether data is available on other nodes; since if the last member is leaving a data loss will occur. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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