April 2012 - mod_cluster-issues - Jboss List Archives

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

by Stefano Nichele (JIRA)

Stefano Nichele created MODCLUSTER-284: ------------------------------------------ Summary: 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 Affects Versions: 1.2.0.Final, 1.1.3.Final Reporter: Stefano Nichele Assignee: Jean-Frederic Clere 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): /** * 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(); } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
5
0 / 0

[JBoss JIRA] (MODCLUSTER-299) REGRESSION - mod_cluster issues an ENABLE-APP too early in the webapp lifecycle

by Gregory Lardiere (JIRA)

Gregory Lardiere created MODCLUSTER-299: ------------------------------------------- Summary: REGRESSION - mod_cluster issues an ENABLE-APP too early in the webapp lifecycle Key: MODCLUSTER-299 URL: https://issues.jboss.org/browse/MODCLUSTER-299 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.4.GA, 1.0.5, 1.1.0.Final Reporter: Gregory Lardiere Assignee: Jean-Frederic Clere Fix For: 1.0.5, 1.0.6, 1.1.1.Final mod_cluster uses START_EVENT instead of AFTER_START_EVENT so it might ENABLE the application too early. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
6
0 / 0

[JBoss JIRA] (MODCLUSTER-301) CLONE - REGRESSION - mod_cluster issues an ENABLE-APP too early in the webapp lifecycle

by Lami Akagwu (JIRA)

Lami Akagwu created MODCLUSTER-301: -------------------------------------- Summary: CLONE - REGRESSION - mod_cluster issues an ENABLE-APP too early in the webapp lifecycle Key: MODCLUSTER-301 URL: https://issues.jboss.org/browse/MODCLUSTER-301 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.10, MOD_CLUSTER_1_0_10_GA_CP02 Environment: JBoss-5.1.0.GA Reporter: Lami Akagwu Assignee: Jean-Frederic Clere Fix For: MOD_CLUSTER_1_0_10_GA_CP03 mod_cluster ENABLE the application too early. The ENABLE-APP message is sent twice : at the beginning AND at the end of the application startup. This is a regression : it worked fine after MODCLUSTER-190 was resolved (r408). It seems that r551 (MODCLUSTER-224) has re-introduced the bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-300) mod_cluster does generate a JVMRoute with EAP5

by Jean-Frederic Clere (JIRA)

Jean-Frederic Clere created MODCLUSTER-300: ---------------------------------------------- Summary: mod_cluster does generate a JVMRoute with EAP5 Key: MODCLUSTER-300 URL: https://issues.jboss.org/browse/MODCLUSTER-300 Project: mod_cluster Issue Type: Bug Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere you get: [Mon Apr 09 18:18:15 2012] [debug] mod_manager.c(2473): manager_handler CONFIG (/) processing: "Port=8009&Host=127.0.0.1&Type=ajp&StickySessionForce=No&Maxattempts=1" [Mon Apr 09 18:18:15 2012] [warn] manager_handler CONFIG error: SYNTAX: JVMRoute can't be empty when you don't configure JvmRoute in the engine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
2
0 / 0

[JBoss JIRA] (MODCLUSTER-290) mod_cluster's mod_advertise can not start on IPv6-only box

by Michal Babacek (JIRA)

Michal Babacek created MODCLUSTER-290: ----------------------------------------- Summary: mod_cluster's mod_advertise can not start on IPv6-only box Key: MODCLUSTER-290 URL: https://issues.jboss.org/browse/MODCLUSTER-290 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.0.Final Environment: Pure IPv6, Apache/2.2.21 (Unix), mod_cluster/1.2.0.Final, Fedora 15 Reporter: Michal Babacek Assignee: Michal Babacek Priority: Blocker Fix For: 1.2.1.Beta1 With the following network configuration on Fedora 15: {noformat} lo Link encap:Local Loopback inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 +++ eth0 Link encap:Ethernet HWaddr 08:00:27:2F:DD:4A inet6 addr: fe80::a00:27ff:fe2f::dd4a/64 Scope:Link inet6 addr: 1:0:0:1::11/128 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 +++ {noformat} and this *Apache/2.2.21* (Unix) *mod_cluster/1.2.0.Final* config: {code:title=httpd.conf|borderStyle=solid|borderColor=#ccc| titleBGColor=#F7D6C1} +++ Listen [1:0:0:1::11]:8000 +++ <IfModule manager_module> Listen [1:0:0:1::11]:6666 ManagerBalancerName mycluster <VirtualHost [1:0:0:1::11]:6666> <Location /> Order deny,allow Deny from all Allow from all </Location> KeepAliveTimeout 300 MaxKeepAliveRequests 0 ServerAdvertise on http://[1:0:0:1::11]:6666 AdvertiseFrequency 5 AdvertiseGroup [ff01::1]:23364 EnableMCPMReceive <Location /mcm> SetHandler mod_cluster-manager Order deny,allow Deny from all Allow from all </Location> </VirtualHost> </IfModule> {code} I get the undermentioned error: {code:title=httpd/logs/error_log|borderStyle=solid|borderColor=#ccc| titleBGColor=#F7D6C1} [Mon Mar 05 13:47:26 2012] [notice] Digest: generating secret for digest authentication ... [Mon Mar 05 13:47:26 2012] [notice] Digest: done [Mon Mar 05 13:47:27 2012] [error] (EAI 9)Address family for hostname not supported: mod_advertise: ma_group_join apr_sockaddr_info_get(ff01::1:23364) failed [Mon Mar 05 13:47:27 2012] [error] (EAI 9)Address family for hostname not supported: mod_advertise: multicast join failed for ff01::1:23364. [Mon Mar 05 13:47:27 2012] [notice] Advertise initialized for process 2157 [Mon Mar 05 13:47:27 2012] [notice] Apache/2.2.21 (Unix) mod_cluster/1.2.0.Final DAV/2 mod_jk/1.2.30 configured -- resuming normal operations {code} , Apache carries on and http://[1:0:0:1::11]:8000/ displays "It works!". What should one do in order to enable IPv6 in *apr* (apr_sockaddr_info_get) ? Do you see any configuration errors? Please, share your ideas and tips... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
13
0 / 0

[JBoss JIRA] (MODCLUSTER-289) MemManagerFile creates directory but put files in ..

by Jean-Frederic Clere (JIRA)

Jean-Frederic Clere created MODCLUSTER-289: ---------------------------------------------- Summary: MemManagerFile creates directory but put files in .. Key: MODCLUSTER-289 URL: https://issues.jboss.org/browse/MODCLUSTER-289 Project: mod_cluster Issue Type: Bug Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 1.2.1.Beta1 MemManagerFile /var/cache/httpd/FILES [root@neo4 jfclere]# ls -lt /var/cache/httpd/ total 28 -rw-r--r--. 1 root root 4 Mar 2 17:05 FILES.domain.domain -rw-r--r--. 1 root root 4 Mar 2 17:05 FILES.balancer.balancers -rw-r--r--. 1 root root 0 Mar 2 17:05 FILES.balancer.balancers.lock -rw-r--r--. 1 root root 0 Mar 2 17:05 FILES.domain.domain.lock -rw-r--r--. 1 root root 4 Mar 2 17:05 FILES.sessionid.sessionid -rw-r--r--. 1 root root 0 Mar 2 17:05 FILES.sessionid.sessionid.lock -rw-r--r--. 1 root root 4 Mar 2 17:05 FILES.context.contexts -rw-r--r--. 1 root root 0 Mar 2 17:05 FILES.context.contexts.lock -rw-r--r--. 1 root root 4 Mar 2 17:05 FILES.host.hosts -rw-r--r--. 1 root root 0 Mar 2 17:05 FILES.host.hosts.lock -rw-r--r--. 1 root root 4 Mar 2 17:05 FILES.node.nodes -rw-r--r--. 1 root root 0 Mar 2 17:05 FILES.node.nodes.lock drwx------. 2 root root 4096 Mar 2 17:05 FILES -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues April 2012