December 2014 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-443) mod_cluster doesn't recognize ; as a proper context delimiter causing 404s on requests with URL jsessionids

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-443?page=com.atlassian.jira.pl... ] Michal Babacek commented on MODCLUSTER-443: ------------------------------------------- 1.2.11.Final -> 1.2.10.Final > mod_cluster doesn't recognize ; as a proper context delimiter causing 404s on requests with URL jsessionids > ----------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-443 > URL: https://issues.jboss.org/browse/MODCLUSTER-443 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.9.Final, 1.3.1.Alpha2 > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.10.Final, 1.3.1.Beta1 > > > This is similar to MODCLUSTER-328, but in regards to ; instead of ?. > mod_cluster does not recognize ; as a delimiter when checking the request context. Thus with no trailing slash on index page requests, it treats ;jsessionid as part of the request context and tries to check the balancer for a deployed context of /helloworld;jsessionid=..., which doesn't exist and 404s. Adding the trailing slash, mod_cluster can properly delimit this and then sees the context (so /helloworld/;jsessionid=... works just fine). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-443) mod_cluster doesn't recognize ; as a proper context delimiter causing 404s on requests with URL jsessionids

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-443?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-443: -------------------------------------- Fix Version/s: 1.2.10.Final (was: 1.2.11.Final) > mod_cluster doesn't recognize ; as a proper context delimiter causing 404s on requests with URL jsessionids > ----------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-443 > URL: https://issues.jboss.org/browse/MODCLUSTER-443 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.9.Final, 1.3.1.Alpha2 > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.10.Final, 1.3.1.Beta1 > > > This is similar to MODCLUSTER-328, but in regards to ; instead of ?. > mod_cluster does not recognize ; as a delimiter when checking the request context. Thus with no trailing slash on index page requests, it treats ;jsessionid as part of the request context and tries to check the balancer for a deployed context of /helloworld;jsessionid=..., which doesn't exist and 404s. Adding the trailing slash, mod_cluster can properly delimit this and then sees the context (so /helloworld/;jsessionid=... works just fine). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-389) standby worker doesn't work.

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-389?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-389. ------------------------------------- Resolution: Done We agreed that with [these fixes|https://issues.jboss.org/browse/MODCLUSTER-389?focusedCommentId=130...], the problem is gone. > standby worker doesn't work. > ---------------------------- > > Key: MODCLUSTER-389 > URL: https://issues.jboss.org/browse/MODCLUSTER-389 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.7.Final, 1.3.0.Final > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.3.1.Beta1, 1.2.9.Final > > > While using <simple-load-provider factor="0"/> (which creates a hoy standby node). > 1- WildFly/AS complain the factor=0 isn't valid. > 2 - the status of the node stays in error. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-389) standby worker doesn't work.

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-389?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-389: -------------------------------------- Fix Version/s: 1.3.1.Beta1 1.2.9.Final (was: 1.2.11.Final) (was: 1.3.1.Beta2) > standby worker doesn't work. > ---------------------------- > > Key: MODCLUSTER-389 > URL: https://issues.jboss.org/browse/MODCLUSTER-389 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.7.Final, 1.3.0.Final > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.2.9.Final, 1.3.1.Beta1 > > > While using <simple-load-provider factor="0"/> (which creates a hoy standby node). > 1- WildFly/AS complain the factor=0 isn't valid. > 2 - the status of the node stays in error. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-443) mod_cluster doesn't recognize ; as a proper context delimiter causing 404s on requests with URL jsessionids

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-443?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-443: ------------------------------------------- Next time, please make sure that "Fix Version/s:" is set before resolving, thanks! > mod_cluster doesn't recognize ; as a proper context delimiter causing 404s on requests with URL jsessionids > ----------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-443 > URL: https://issues.jboss.org/browse/MODCLUSTER-443 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.9.Final, 1.3.1.Alpha2 > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.3.1.Beta1, 1.2.11.Final > > > This is similar to MODCLUSTER-328, but in regards to ; instead of ?. > mod_cluster does not recognize ; as a delimiter when checking the request context. Thus with no trailing slash on index page requests, it treats ;jsessionid as part of the request context and tries to check the balancer for a deployed context of /helloworld;jsessionid=..., which doesn't exist and 404s. Adding the trailing slash, mod_cluster can properly delimit this and then sees the context (so /helloworld/;jsessionid=... works just fine). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-441) Upgrade Tomcat 8 support to 8.0.16 due to OPTIONS * broken (BZ#57187)

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-441?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-441: ------------------------------------------- Update: still waiting for the release, latest is 8.0.15 (http://tomcat.apache.org/download-80.cgi). > Upgrade Tomcat 8 support to 8.0.16 due to OPTIONS * broken (BZ#57187) > --------------------------------------------------------------------- > > Key: MODCLUSTER-441 > URL: https://issues.jboss.org/browse/MODCLUSTER-441 > Project: mod_cluster > Issue Type: Task > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.1.Beta2 > > > https://issues.apache.org/bugzilla/show_bug.cgi?id=57187 > ..and after this we can announce proper Tomcat 8 suport with HTTP connections for community to test. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-441) Upgrade Tomcat 8 support to 8.0.16 due to OPTIONS * broken (BZ#57187)

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-441?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-441: -------------------------------------- Component/s: Core & Container Integration (Java) > Upgrade Tomcat 8 support to 8.0.16 due to OPTIONS * broken (BZ#57187) > --------------------------------------------------------------------- > > Key: MODCLUSTER-441 > URL: https://issues.jboss.org/browse/MODCLUSTER-441 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.1.Beta2 > > > https://issues.apache.org/bugzilla/show_bug.cgi?id=57187 > ..and after this we can announce proper Tomcat 8 suport with HTTP connections for community to test. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

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

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-303?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-303: -------------------------------------- Fix Version/s: 1.3.1.Beta2 (was: 1.3.1.Beta1) > 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 > Fix For: 1.3.1.Beta2 > > > 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 (v6.3.11#6341)

10 years

1
0
0 / 0

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

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-282?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-282: -------------------------------------- Fix Version/s: 1.3.1.Beta2 (was: 1.3.1.Beta1) > Add JGroups support > ------------------- > > Key: MODCLUSTER-282 > URL: https://issues.jboss.org/browse/MODCLUSTER-282 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.0.Final > Reporter: Jean-Frederic Clere > Assignee: Radoslav Husar > Fix For: 1.3.1.Beta2 > > > https://community.jboss.org/wiki/MOD-CLUSTERDiscoveryProtocol -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-168: -------------------------------------- Fix Version/s: 1.3.1.Beta2 (was: 1.3.1.Beta1) > mod_cluster should use hostname provided in address instead a IP address > ------------------------------------------------------------------------ > > Key: MODCLUSTER-168 > URL: https://issues.jboss.org/browse/MODCLUSTER-168 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.1.0.CR3 > Environment: any > Reporter: Jean-Frederic Clere > Assignee: Radoslav Husar > Fix For: 1.2.11.Final, 1.3.1.Beta2 > > > The CONFIG message contains something like: > JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp > Even if the Connector is defined like: > <Connector port="8009" address= "jfcpc" protocol="AJP/1.3" redirectPort="8443" /> > There are 2 ways to fix: > - Use the String (Change the Connector.java in mod_cluster). > - Use parameters.put("Host", connector.getAddress().getHostName()); when building the CONFIG message. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues December 2014