November 2014 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-427) mod_cluster can break stickiness for the first request on new child processes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-427?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on MODCLUSTER-427: ---------------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1136976|https://bugzilla.redhat.com/show_bug.cgi?id=1136976] from MODIFIED to ON_QA > mod_cluster can break stickiness for the first request on new child processes > ----------------------------------------------------------------------------- > > Key: MODCLUSTER-427 > URL: https://issues.jboss.org/browse/MODCLUSTER-427 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.9.Final, 1.3.1.Alpha1 > Environment: JBoss EAP 6.3.0 > Reporter: Aaron Ogburn > Assignee: Aaron Ogburn > Fix For: 1.2.10.Final, 1.3.1.Alpha3 > > > mod_cluster can break stickiness for the first request on new child processes. It looks like this occurs specifically when "CreateBalancers 1" is used. Prefork typically makes this much worse as well. > My debugging showed that the proxy_balancer would exist, but it would essentially be empty in the new child process. find_session_route/find_route_worker would be called as expected, but the for loop in find_route_worker wasn't even doing anything because balancer->workers->nelts was 0. The balancer would then finally be populated in the new child when the first request hits internal_find_best_byrequests and calls update_workers_node. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

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 RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-443?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated MODCLUSTER-443: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1164916 > 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 > > 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.8#6338)

9 years, 5 months

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 Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-443?page=com.atlassian.jira.pl... ] Aaron Ogburn updated MODCLUSTER-443: ------------------------------------ Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/131, https://github.com/modcluster/mod_cluster/pull/132 (was: https://github.com/modcluster/mod_cluster/pull/131) > 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 > > 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.8#6338)

9 years, 5 months

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 Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-443?page=com.atlassian.jira.pl... ] Aaron Ogburn updated MODCLUSTER-443: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/131 > 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 > > 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.8#6338)

9 years, 5 months

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 Aaron Ogburn (JIRA)

Aaron Ogburn created MODCLUSTER-443: --------------------------------------- Summary: 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.3.1.Alpha2, 1.2.9.Final Reporter: Aaron Ogburn Assignee: Jean-Frederic Clere 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.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-427) mod_cluster can break stickiness for the first request on new child processes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-427?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on MODCLUSTER-427: ---------------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1136976|https://bugzilla.redhat.com/show_bug.cgi?id=1136976] from POST to MODIFIED > mod_cluster can break stickiness for the first request on new child processes > ----------------------------------------------------------------------------- > > Key: MODCLUSTER-427 > URL: https://issues.jboss.org/browse/MODCLUSTER-427 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.9.Final, 1.3.1.Alpha1 > Environment: JBoss EAP 6.3.0 > Reporter: Aaron Ogburn > Assignee: Aaron Ogburn > Fix For: 1.2.10.Final, 1.3.1.Alpha3 > > > mod_cluster can break stickiness for the first request on new child processes. It looks like this occurs specifically when "CreateBalancers 1" is used. Prefork typically makes this much worse as well. > My debugging showed that the proxy_balancer would exist, but it would essentially be empty in the new child process. find_session_route/find_route_worker would be called as expected, but the for loop in find_route_worker wasn't even doing anything because balancer->workers->nelts was 0. The balancer would then finally be populated in the new child when the first request hits internal_find_best_byrequests and calls update_workers_node. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-442) Can't build mod_cluster from master

by Maxime Beck (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-442?page=com.atlassian.jira.pl... ] Maxime Beck reopened MODCLUSTER-442: ------------------------------------ > Can't build mod_cluster from master > ----------------------------------- > > Key: MODCLUSTER-442 > URL: https://issues.jboss.org/browse/MODCLUSTER-442 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.1.Alpha2 > Reporter: Maxime Beck > Assignee: Radoslav Husar > Labels: mod_cluster > > When trying to build mod_cluster from it's github repository (version 1.3.1.Alpha2), I get two failures on the core module as seen bellow. > $ mvn install > ++++ > Results : > Failed tests: > AdvertiseListenerImplTestCase.testBasicOperation:135 > Wanted but not invoked: > mCMPHandler.addProxy(<Capturing argument>); > -> at org.jboss.modcluster.advertise.AdvertiseListenerImplTestCase.testBasicOperation(AdvertiseListenerImplTestCase.java:135) > Actually, there were zero interactions with this mock. > MulticastSocketFactoryImplTestCase.testMulticastSocketNoCrossTalk:63->testMulticastSocket:112 null > Tests run: 46, Failures: 2, Errors: 0, Skipped: 0 > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] mod_cluster (parent) ............................... SUCCESS [ 0.618 s] > [INFO] mod_cluster: Container SPI ......................... SUCCESS [ 0.412 s] > [INFO] mod_cluster: Core .................................. FAILURE [ 4.163 s] > [INFO] mod_cluster: Container (parent) .................... SKIPPED > [INFO] mod_cluster: Container - Catalina .................. SKIPPED > [INFO] mod_cluster: Container - Catalina (standalone) ..... SKIPPED > [INFO] mod_cluster: Container - Tomcat 6 .................. SKIPPED > [INFO] mod_cluster: Container - Tomcat 7 .................. SKIPPED > [INFO] mod_cluster: Container - Tomcat 8 .................. SKIPPED > [INFO] mod_cluster: Container - JBoss Web ................. SKIPPED > [INFO] mod_cluster: Demo (parent) ......................... SKIPPED > [INFO] mod_cluster: Demo - Client ......................... SKIPPED > [INFO] mod_cluster: Demo - Server ......................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 5.506 s > [INFO] Finished at: 2014-11-12T18:04:39+01:00 > [INFO] Final Memory: 15M/298M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project mod_cluster-core: There are test failures. > [ERROR] > [ERROR] Please refer to /home/mbeck/dev/mod_cluster/core/target/surefire-reports for the individual test results. > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <goals> -rf :mod_cluster-core > +++ -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-442) Can't build mod_cluster from master

by Maxime Beck (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-442?page=com.atlassian.jira.pl... ] Maxime Beck closed MODCLUSTER-442. ---------------------------------- Resolution: Done > Can't build mod_cluster from master > ----------------------------------- > > Key: MODCLUSTER-442 > URL: https://issues.jboss.org/browse/MODCLUSTER-442 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.1.Alpha2 > Reporter: Maxime Beck > Assignee: Radoslav Husar > Labels: mod_cluster > > When trying to build mod_cluster from it's github repository (version 1.3.1.Alpha2), I get two failures on the core module as seen bellow. > $ mvn install > ++++ > Results : > Failed tests: > AdvertiseListenerImplTestCase.testBasicOperation:135 > Wanted but not invoked: > mCMPHandler.addProxy(<Capturing argument>); > -> at org.jboss.modcluster.advertise.AdvertiseListenerImplTestCase.testBasicOperation(AdvertiseListenerImplTestCase.java:135) > Actually, there were zero interactions with this mock. > MulticastSocketFactoryImplTestCase.testMulticastSocketNoCrossTalk:63->testMulticastSocket:112 null > Tests run: 46, Failures: 2, Errors: 0, Skipped: 0 > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] mod_cluster (parent) ............................... SUCCESS [ 0.618 s] > [INFO] mod_cluster: Container SPI ......................... SUCCESS [ 0.412 s] > [INFO] mod_cluster: Core .................................. FAILURE [ 4.163 s] > [INFO] mod_cluster: Container (parent) .................... SKIPPED > [INFO] mod_cluster: Container - Catalina .................. SKIPPED > [INFO] mod_cluster: Container - Catalina (standalone) ..... SKIPPED > [INFO] mod_cluster: Container - Tomcat 6 .................. SKIPPED > [INFO] mod_cluster: Container - Tomcat 7 .................. SKIPPED > [INFO] mod_cluster: Container - Tomcat 8 .................. SKIPPED > [INFO] mod_cluster: Container - JBoss Web ................. SKIPPED > [INFO] mod_cluster: Demo (parent) ......................... SKIPPED > [INFO] mod_cluster: Demo - Client ......................... SKIPPED > [INFO] mod_cluster: Demo - Server ......................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 5.506 s > [INFO] Finished at: 2014-11-12T18:04:39+01:00 > [INFO] Final Memory: 15M/298M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project mod_cluster-core: There are test failures. > [ERROR] > [ERROR] Please refer to /home/mbeck/dev/mod_cluster/core/target/surefire-reports for the individual test results. > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <goals> -rf :mod_cluster-core > +++ -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-439) Installation for Tomcat 6/7/8 is cumbersome, revamp distribution profile

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-439?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-439: -------------------------------------- Summary: Installation for Tomcat 6/7/8 is cumbersome, revamp distribution profile (was: Installation for Tomcat 6/7/8 is cumbersome, improve distribution profile) > Installation for Tomcat 6/7/8 is cumbersome, revamp distribution profile > ------------------------------------------------------------------------ > > Key: MODCLUSTER-439 > URL: https://issues.jboss.org/browse/MODCLUSTER-439 > Project: mod_cluster > Issue Type: Feature Request > Components: Documentation & Demos > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: tomcat > Fix For: 1.3.1.Alpha3 > > > The installation in the docs now expects to go around and copy lots of jars to the /lib dir, the package we ship has all the tomcat 6 and 7 jars in the same spot... we shoud align this to be easier and/or include a readme file in the directory. Also update the documentation for people bulding from source. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-439) Installation for Tomcat 6/7/8 is cumbersome, revamp distribution profile

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-439?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-439: ------------------------------------------- I would also like to move the distribution aspects of the project to /distribution and build the /sar and bundles there. > Installation for Tomcat 6/7/8 is cumbersome, revamp distribution profile > ------------------------------------------------------------------------ > > Key: MODCLUSTER-439 > URL: https://issues.jboss.org/browse/MODCLUSTER-439 > Project: mod_cluster > Issue Type: Feature Request > Components: Documentation & Demos > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: tomcat > Fix For: 1.3.1.Alpha3 > > > The installation in the docs now expects to go around and copy lots of jars to the /lib dir, the package we ship has all the tomcat 6 and 7 jars in the same spot... we shoud align this to be easier and/or include a readme file in the directory. Also update the documentation for people bulding from source. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues November 2014