October 2016 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-539) Support JDK9 build 9-ea+139

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-539?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-539: -------------------------------------- Description: The compiler parameters changed. > Support JDK9 build 9-ea+139 > --------------------------- > > Key: MODCLUSTER-539 > URL: https://issues.jboss.org/browse/MODCLUSTER-539 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Labels: jdk9 > > The compiler parameters changed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-539) Support JDK9 build 9-ea+139

by Radoslav Husar (JIRA)

Radoslav Husar created MODCLUSTER-539: ----------------------------------------- Summary: Support JDK9 build 9-ea+139 Key: MODCLUSTER-539 URL: https://issues.jboss.org/browse/MODCLUSTER-539 Project: mod_cluster Issue Type: Feature Request Components: Core & Container Integration (Java) Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-502) Upgrade MulticastSocket to MulticastChannel

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-502?page=com.atlassian.jira.pl... ] Work on MODCLUSTER-502 started by Radoslav Husar. ------------------------------------------------- > Upgrade MulticastSocket to MulticastChannel > ------------------------------------------- > > Key: MODCLUSTER-502 > URL: https://issues.jboss.org/browse/MODCLUSTER-502 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > * upgrade requirement to JDK7 > * simply AdvertiseListenerImpl > * remove unused AdvertiseListener lifecycle methods with AutoCloseable > * add tests on IPv6 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-497) ModClusterConfig#setAdvertiseInterface(java.lang.String) should not have been deprecated as it's used by Tomcat modeller

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-497?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-497: -------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ModClusterConfig#setAdvertiseInterface(java.lang.String) should not have been deprecated as it's used by Tomcat modeller > ------------------------------------------------------------------------------------------------------------------------ > > Key: MODCLUSTER-497 > URL: https://issues.jboss.org/browse/MODCLUSTER-497 > Project: mod_cluster > Issue Type: Bug > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > This may be causing some confusions in JWS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-498) Extract Tomcat modeler specific methods from ModClusterConfig into separate Tomcat-specific class

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-498?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-498: -------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Extract Tomcat modeler specific methods from ModClusterConfig into separate Tomcat-specific class > ------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-498 > URL: https://issues.jboss.org/browse/MODCLUSTER-498 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > This has been polluting the API for a while now. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-457) Tomcat mod_cluster integration does not allow one to choose a connector

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-457?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-457: -------------------------------------- Workaround: Workaround Exists > Tomcat mod_cluster integration does not allow one to choose a connector > ----------------------------------------------------------------------- > > Key: MODCLUSTER-457 > URL: https://issues.jboss.org/browse/MODCLUSTER-457 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.2.11.Final, 1.3.1.Final > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Fix For: 1.3.4.Final > > > Configuring mod_cluster to leverage {{ws://}} with {{EnableWsTunnel}} (mod_proxy_wstunnel) requires the Tomcat to use *http* instead of *ajp* connector. > Unlike [AS7/WildFly/EAP|https://github.com/wildfly/wildfly/blob/master/mod_cluste...] mod_cluster integration, the Tomcat one ignores such option, i.e. there is nothing about selecting a particular connector with a *connector* attribute in [mbeans-descriptors.xml|https://github.com/modcluster/mod_cluster/blob/b3a...]. > <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" > {color:red}*connector="http"*{color} advertiseGroupAddress="224.0.5.12" advertisePort="61217" > /> > Suggestion: Let's add the option to the catalina integration as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-522) Memory leak in processing MCMP, wrong apr pool used for allocation

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-522?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-522: ------------------------------------------------ I committed (and tested) in the 1.3.x branch but not in master (https://github.com/modcluster/mod_proxy_cluster) > Memory leak in processing MCMP, wrong apr pool used for allocation > ------------------------------------------------------------------ > > Key: MODCLUSTER-522 > URL: https://issues.jboss.org/browse/MODCLUSTER-522 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final, 2.0.0.Alpha1 > Environment: Solaris 10 x86_64, RHEL 6, Fedora 24, httpd 2.4.6, httpd 2.4.20 > Reporter: Michal Karm Babacek > Assignee: Jean-Frederic Clere > Priority: Critical > Attachments: mod_cluster-mem.jpg, mod_cluster-mem1.jpg > > > There seems to be a wrong apr pool used for processing certain MCMP commands. We should use short life span pools for immediate processing and server-lifetime pools only for really persistent configuration. In the current state, with 20+ tomcat workers (1 alias and 1 context each) and virtually no client requests, we could see slow, but steady growth of heap allocated memory. > TODO: Investigate the offending logic, make sure we ain't using long-lived pools for immediate processing. > Originally discovered by: [~j_sykora] and [~jmsantuci] > Illustrative memory overview - with constant number of Tomcats: > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-522) Memory leak in processing MCMP, wrong apr pool used for allocation

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-522?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-522: ------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/mod_proxy_cluster/pull/6 upstream fix. > Memory leak in processing MCMP, wrong apr pool used for allocation > ------------------------------------------------------------------ > > Key: MODCLUSTER-522 > URL: https://issues.jboss.org/browse/MODCLUSTER-522 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final, 2.0.0.Alpha1 > Environment: Solaris 10 x86_64, RHEL 6, Fedora 24, httpd 2.4.6, httpd 2.4.20 > Reporter: Michal Karm Babacek > Assignee: Jean-Frederic Clere > Priority: Critical > Attachments: mod_cluster-mem.jpg, mod_cluster-mem1.jpg > > > There seems to be a wrong apr pool used for processing certain MCMP commands. We should use short life span pools for immediate processing and server-lifetime pools only for really persistent configuration. In the current state, with 20+ tomcat workers (1 alias and 1 context each) and virtually no client requests, we could see slow, but steady growth of heap allocated memory. > TODO: Investigate the offending logic, make sure we ain't using long-lived pools for immediate processing. > Originally discovered by: [~j_sykora] and [~jmsantuci] > Illustrative memory overview - with constant number of Tomcats: > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-522) Memory leak in processing MCMP, wrong apr pool used for allocation

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-522?page=com.atlassian.jira.pl... ] Michal Karm Babacek reassigned MODCLUSTER-522: ---------------------------------------------- Assignee: Jean-Frederic Clere (was: Michal Karm Babacek) > Memory leak in processing MCMP, wrong apr pool used for allocation > ------------------------------------------------------------------ > > Key: MODCLUSTER-522 > URL: https://issues.jboss.org/browse/MODCLUSTER-522 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final, 2.0.0.Alpha1 > Environment: Solaris 10 x86_64, RHEL 6, Fedora 24, httpd 2.4.6, httpd 2.4.20 > Reporter: Michal Karm Babacek > Assignee: Jean-Frederic Clere > Priority: Critical > Attachments: mod_cluster-mem.jpg, mod_cluster-mem1.jpg > > > There seems to be a wrong apr pool used for processing certain MCMP commands. We should use short life span pools for immediate processing and server-lifetime pools only for really persistent configuration. In the current state, with 20+ tomcat workers (1 alias and 1 context each) and virtually no client requests, we could see slow, but steady growth of heap allocated memory. > TODO: Investigate the offending logic, make sure we ain't using long-lived pools for immediate processing. > Originally discovered by: [~j_sykora] and [~jmsantuci] > Illustrative memory overview - with constant number of Tomcats: > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues October 2016