May 2019 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-694) Segfaults with httpd-2.4.39-2.fc29.x86_64, conn_rec/request_rec, core on myConnConfig(r->connection);

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-694?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-694: ------------------------------------------- Fix Version/s: 1.3.11.Final 2.0.0.Alpha2 > Segfaults with httpd-2.4.39-2.fc29.x86_64, conn_rec/request_rec, core on myConnConfig(r->connection); > ------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-694 > URL: https://issues.jboss.org/browse/MODCLUSTER-694 > Project: mod_cluster > Issue Type: Bug > Environment: httpd-2.4.39-2.fc29.x86_64 > Reporter: Michal Karm > Assignee: Michal Karm > Priority: Blocker > Fix For: 1.3.11.Final, 2.0.0.Alpha2 > > > See https://bugzilla.redhat.com/show_bug.cgi?id=1705574 -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-694) Segfaults with httpd-2.4.39-2.fc29.x86_64, conn_rec/request_rec, core on myConnConfig(r->connection);

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-694?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-694: ------------------------------------------------ https://github.com/modcluster/mod_proxy_cluster/commit/7a62cbf471bcfaf3af... fixes it. > Segfaults with httpd-2.4.39-2.fc29.x86_64, conn_rec/request_rec, core on myConnConfig(r->connection); > ------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-694 > URL: https://issues.jboss.org/browse/MODCLUSTER-694 > Project: mod_cluster > Issue Type: Bug > Environment: httpd-2.4.39-2.fc29.x86_64 > Reporter: Michal Karm > Assignee: Michal Karm > Priority: Blocker > > See https://bugzilla.redhat.com/show_bug.cgi?id=1705574 -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-54) Use slotmems from httpd-trunk

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-54?page=com.atlassian.jira.plu... ] Jean-Frederic Clere updated MODCLUSTER-54: ------------------------------------------ Fix Version/s: 2.0.0.Alpha2 > Use slotmems from httpd-trunk > ----------------------------- > > Key: MODCLUSTER-54 > URL: https://issues.jboss.org/browse/MODCLUSTER-54 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Environment: mod_cluster httpd-trunk > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Priority: Minor > Fix For: 2.0.0.Alpha2 > > > My old code of httpd-proxy-scoreboard has been moved to httpd-trunk we should stop using our own "forked" version of slotmems. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-74) Simplifiy the slotmem logic to use httpd-trunk one

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-74?page=com.atlassian.jira.plu... ] Jean-Frederic Clere updated MODCLUSTER-74: ------------------------------------------ Fix Version/s: 2.0.0.Alpha2 > Simplifiy the slotmem logic to use httpd-trunk one > -------------------------------------------------- > > Key: MODCLUSTER-74 > URL: https://issues.jboss.org/browse/MODCLUSTER-74 > Project: mod_cluster > Issue Type: Feature Request > Environment: Code > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Priority: Minor > Fix For: 2.0.0.Alpha2 > > > The slomem in httpd-trunk is quite different from the one we use. We should try to use common code. > httpd doesn't use a alloc/free logic. > httpd lock should be remove (dev list decision and it makes sense). -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-186) Proxy Discovery Configuration property excludedContexts is not set to default when running under Tomcat

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-186?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-186. -------------------------------------------- Resolution: Out of Date > Proxy Discovery Configuration property excludedContexts is not set to default when running under Tomcat > ------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-186 > URL: https://issues.jboss.org/browse/MODCLUSTER-186 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.1.0.Final > Environment: Tomcat 6.0.29 > Reporter: Ruslan Gainutdinov > Assignee: Jean-Frederic Clere > Priority: Major > Labels: mod_cluster, tomcat > > The documentation > http://docs.jboss.org/mod_cluster/1.1.0/html/java.properties.html > states that excludedContexts have default value of > ROOT, admin-console, invoker, bossws, jmx-console, juddi, web-console > However, under Tomcat, it is not the case. > When org.jboss.modcluster.ModClusterService.init() is called mcmpConfig.excludedContexts is null. > One have to manually specify > <Listener className="org.jboss.modcluster.catalina.ModClusterListener" > excludedContexts="ROOT,manager,host-manager"/> > Best fix will be to set it excludedContexts="ROOT,manager,host-manager" > as default under Tomcat. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-284) remove_session_route doesn't work as expected with session id in the URL

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-284?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-284. -------------------------------------------- Resolution: Out of Date > remove_session_route doesn't work as expected with session id in the URL > ------------------------------------------------------------------------ > > Key: MODCLUSTER-284 > URL: https://issues.jboss.org/browse/MODCLUSTER-284 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.1.3.Final, 1.2.0.Final > Reporter: Stefano Nichele > Assignee: Jean-Frederic Clere > Priority: Major > > Looking at the code of remove_session_route (and trying it) i saw that URLs lke this one > /test.jsp;jsessionid=1233454532432342.NODE01 > /test.jsp;jsessionid=1233454532432342.NODE01?p1=v1&p2=v2 > /test.jsp;jsessionid=1233454532432342.NODE01;otherparam=value > are not correctly parsed and the session id is not removed. > To note that it seems the code handles jsessionid as url parameter and not as URL "path parameter" (see for isntance http://doriantaylor.com/policy/http-url-path-parameter-syntax). > This is for instance a piece of tomcat code that does something like what remove_session_route should do (at least in the URL part): > {code} > /** > * Strips a servlet session ID from <tt>url</tt>. The session ID > * is encoded as a URL "path parameter" beginning with "jsessionid=". > * We thus remove anything we find between ";jsessionid=" (inclusive) > * and either EOS or a subsequent ';' (exclusive). > * > * taken from org.apache.taglibs.standard.tag.common.core.ImportSupport > */ > public static String stripSession(String url) { > StringBuffer u = new StringBuffer(url); > int sessionStart; > while ((sessionStart = u.toString().indexOf(";jsessionid=")) != -1) { > int sessionEnd = u.toString().indexOf(";", sessionStart + 1); > if (sessionEnd == -1) > sessionEnd = u.toString().indexOf("?", sessionStart + 1); > if (sessionEnd == -1) // still > sessionEnd = u.length(); > u.delete(sessionStart, sessionEnd); > } > return u.toString(); > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-282) Add JGroups support

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-282?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-282. -------------------------------------------- Resolution: Rejected > Add JGroups support > ------------------- > > Key: MODCLUSTER-282 > URL: https://issues.jboss.org/browse/MODCLUSTER-282 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java), Native (httpd modules) > Affects Versions: 1.2.0.Final > Reporter: Jean-Frederic Clere > Assignee: Radoslav Husar > Priority: Major > Fix For: 2.0.0.Alpha1 > > > https://community.jboss.org/wiki/MOD-CLUSTERDiscoveryProtocol -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-287) Demo load servlet needs to be rewritten to not rely on JMX.

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-287?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-287. -------------------------------------------- Resolution: Out of Date > Demo load servlet needs to be rewritten to not rely on JMX. > ----------------------------------------------------------- > > Key: MODCLUSTER-287 > URL: https://issues.jboss.org/browse/MODCLUSTER-287 > Project: mod_cluster > Issue Type: Bug > Components: Documentation & Demos > Affects Versions: 1.2.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-292) Use "MulticastSocket(SocketAddress bindaddr)" on Solaris

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-292?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-292. -------------------------------------------- Resolution: Out of Date > Use "MulticastSocket(SocketAddress bindaddr)" on Solaris > -------------------------------------------------------- > > Key: MODCLUSTER-292 > URL: https://issues.jboss.org/browse/MODCLUSTER-292 > Project: mod_cluster > Issue Type: Task > Affects Versions: 1.2.0.Final > Reporter: Brian Stansberry > Assignee: Radoslav Husar > Priority: Major > > MulticastSocketFactoryImpl determines whether it can use the "MulticastSocket(SocketAddress bindaddr)" constructor variant based on this: > this.linuxlike = (value != null) && (value.toLowerCase().startsWith("linux") || value.toLowerCase().startsWith("mac") || value.toLowerCase().startsWith("hp")); > JGroups when doing a similiar test also allows Solaris via including (value.toLowerCase().startsWith("sun") in the test. > (Tangent: JGroups doesn't allow "mac", which sounds like a good topic for discussion between the respective teams.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-303) Discovery protocol based on mod-cluster

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-303?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-303. -------------------------------------------- Resolution: Rejected > Discovery protocol based on mod-cluster > --------------------------------------- > > Key: MODCLUSTER-303 > URL: https://issues.jboss.org/browse/MODCLUSTER-303 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Vladimir Blagojevic > Assignee: Radoslav Husar > Priority: Major > Fix For: 2.0.0.Alpha1 > > > In it previous life used to be https://issues.jboss.org/browse/JGRP-1322 > It would be nice to have a discovery protocol that can use mod-cluster as the source of the node information. > Mod-cluster already knows the list of participating nodes and provides this information in a well known format, so it could be simple to implement. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 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 2019