November 2014 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-444) MODCLUSTER000043: Failed to send - Connection refused exception using JBOSS 6.3.2

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-444?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-444. -------------------------------------------- Resolution: Rejected That isn't a bug but probably a miscinfiguration or a network issue. Please use the user forum to get help. > MODCLUSTER000043: Failed to send - Connection refused exception using JBOSS 6.3.2 > --------------------------------------------------------------------------------- > > Key: MODCLUSTER-444 > URL: https://issues.jboss.org/browse/MODCLUSTER-444 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Siddharth GARG > Assignee: Jean-Frederic Clere > > We are using JBOSS version 6.3.2 and getting below exception while trying to access the application deployed on it - > MODCLUSTER000043: Failed to send STATUS to server1: java.net.ConnectException: Connection refused > at java.net.PlainSocketImpl.socketConnect(Native Method) [rt.jar:1.7.0_71] > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) [rt.jar:1.7.0_71] > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) [rt.jar:1.7.0_71] > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) [rt.jar:1.7.0_71] > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) [rt.jar:1.7.0_71] > at java.net.Socket.connect(Socket.java:579) [rt.jar:1.7.0_71] > at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler$Proxy.getConnection(DefaultMCMPHandler.java:835) > at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler$Proxy.getConnectionWriter(DefaultMCMPHandler.java:858) > at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.sendRequest(DefaultMCMPHandler.java:499) > at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.sendRequest(DefaultMCMPHandler.java:600) > at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.sendRequest(DefaultMCMPHandler.java:414) > at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:468) > at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:249) > at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.4.9.Final-redhat-1.jar:7.4.9.Final-redhat-1] > at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1323) [jbossweb-7.4.9.Final-redhat-1.jar:7.4.9.Final-redhat-1] > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1588) [jbossweb-7.4.9.Final-redhat-1.jar:7.4.9.Final-redhat-1] > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1574) [jbossweb-7.4.9.Final-redhat-1.jar:7.4.9.Final-redhat-1] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71] > Could you please let me know if this is known issue/bug with JBOSS 6.3.2 and if there is any fix pack available for this > Thanks, -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-444) MODCLUSTER000043: Failed to send - Connection refused exception using JBOSS 6.3.2

by Siddharth GARG (JIRA)

Siddharth GARG created MODCLUSTER-444: ----------------------------------------- Summary: MODCLUSTER000043: Failed to send - Connection refused exception using JBOSS 6.3.2 Key: MODCLUSTER-444 URL: https://issues.jboss.org/browse/MODCLUSTER-444 Project: mod_cluster Issue Type: Feature Request Reporter: Siddharth GARG Assignee: Jean-Frederic Clere We are using JBOSS version 6.3.2 and getting below exception while trying to access the application deployed on it - MODCLUSTER000043: Failed to send STATUS to server1: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) [rt.jar:1.7.0_71] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) [rt.jar:1.7.0_71] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) [rt.jar:1.7.0_71] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) [rt.jar:1.7.0_71] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) [rt.jar:1.7.0_71] at java.net.Socket.connect(Socket.java:579) [rt.jar:1.7.0_71] at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler$Proxy.getConnection(DefaultMCMPHandler.java:835) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler$Proxy.getConnectionWriter(DefaultMCMPHandler.java:858) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.sendRequest(DefaultMCMPHandler.java:499) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.sendRequest(DefaultMCMPHandler.java:600) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.sendRequest(DefaultMCMPHandler.java:414) at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:468) at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:249) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.4.9.Final-redhat-1.jar:7.4.9.Final-redhat-1] at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1323) [jbossweb-7.4.9.Final-redhat-1.jar:7.4.9.Final-redhat-1] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1588) [jbossweb-7.4.9.Final-redhat-1.jar:7.4.9.Final-redhat-1] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1574) [jbossweb-7.4.9.Final-redhat-1.jar:7.4.9.Final-redhat-1] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71] Could you please let me know if this is known issue/bug with JBOSS 6.3.2 and if there is any fix pack available for this Thanks, -- This message was sent by Atlassian JIRA (v6.3.8#6338)

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

[ https://issues.jboss.org/browse/MODCLUSTER-443?page=com.atlassian.jira.pl... ] Aaron Ogburn commented on MODCLUSTER-443: ----------------------------------------- Thanks, [~mbabacek]! > 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)

10 years, 1 month

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 commented on MODCLUSTER-443: ------------------------------------------- Well, the problem was located exactly between the chair and my keyboard. I'm sorry. {quote} http://192.168.122.172:8080/tses;jsessionid=Qq7acr8AUL+212-o9bDcgtTJ.jbos... {quote} The test executed with _worker's_ port, not the balancer's one. With this fixed, indeed, now it doesn't work: Works with EAP worker: {code} curl 'http://192.168.122.172:8080/tses;jsessionid=HfYUfMkbXbaeKZ+SpgQbVqd5.jbos...' <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>Session Test</title> </head> <body> <h3>Server info</h3> <ul> <li>Jsessionid: HfYUfMkbXbaeKZ+SpgQbVqd5.jboss-eap-6.4</li> </ul> </body> </html> {code} Doesn't work via balancer: {code} curl 'http://192.168.122.172:8847/tses;jsessionid=HfYUfMkbXbaeKZ+SpgQbVqd5.jbos...' <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /tses;jsessionid=HfYUfMkbXbaeKZ+SpgQbVqd5.jboss-eap-6.4 was not found on this server.</p> <hr> <address>Apache/2.2.26 (Red Hat Enterprise Web Server) Server at 192.168.122.172 Port 8847</address> </body></html> {code} The test is amended and added to the continuous QA cycle now. > 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)

10 years, 1 month

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: ---------------------------------------------------- Michal Babacek <mbabacek(a)redhat.com> changed the Status of [bug 1136976|https://bugzilla.redhat.com/show_bug.cgi?id=1136976] from ON_QA to ASSIGNED > 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)

10 years, 1 month

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 edited comment on MODCLUSTER-443 at 11/18/14 10:37 AM: -------------------------------------------------------------------- I'm able to reproduce the customer issue consistently with the latest versions. Extra debug logs were showing that find_node_context_host includes the ;jsessionid in the context that it searches for on the balancer: {code} [Mon Nov 17 15:40:01 2014] [debug] mod_proxy_cluster.c(2948): proxy_cluster_trans for 0 (null) (null) uri: /helloworld;jsessionid=blablabla args: (null) unparsed_uri: /helloworld;jsessionid=blablabla [Mon Nov 17 15:40:01 2014] [debug] mod_proxy_cluster.c(2769): cluster: balancer://mycluster Found value blablabla for stickysession JSESSIONID|jsessionid [Mon Nov 17 15:40:01 2014] [debug] mod_proxy_cluster.c(2769): cluster: balancer://mycluster Found value blablabla for stickysession JSESSIONID|jsessionid [Mon Nov 17 15:40:01 2014] [debug] mod_proxy_cluster.c(1943): find_node_context_host: /helloworld;jsessionid=blablabla node: 1 vhost: 1 context: /helloworld [Mon Nov 17 15:40:01 2014] [debug] mod_proxy_cluster.c(3012): proxy_cluster_trans DECLINED (null) uri: (null) unparsed_uri: /helloworld;jsessionid=blablabla [Mon Nov 17 15:40:01 2014] [error] [client 127.0.0.1] File does not exist: /apache/htdocs/helloworld;jsessionid=blablabla {code} So we can't even get a "/context;jsessionid=..." request to proxy from httpd to JBoss through mod_cluster. Session data and servlet mappings don't enter the equation. was (Author: aogburn): I'm able to reproduce the customer issue consistently with the latest versions. Extra debug logs were showing that find_node_context_host includes the ;jsessionid in the context that it searches for on the balancer: {code} [Mon Nov 17 15:40:01 2014] [debug] mod_proxy_cluster.c(2948): proxy_cluster_trans for 0 (null) (null) uri: /helloworld;jsessionid=blablabla args: (null) unparsed_uri: /helloworld;jsessionid=blablabla [Mon Nov 17 15:40:01 2014] [debug] mod_proxy_cluster.c(2769): cluster: balancer://mycluster Found value blablabla for stickysession JSESSIONID|jsessionid [Mon Nov 17 15:40:01 2014] [debug] mod_proxy_cluster.c(2769): cluster: balancer://mycluster Found value blablabla for stickysession JSESSIONID|jsessionid [Mon Nov 17 15:40:01 2014] [debug] mod_proxy_cluster.c(1943): find_node_context_host: /helloworld;jsessionid=blablabla node: 1 vhost: 1 context: /helloworld [Mon Nov 17 15:40:01 2014] [debug] mod_proxy_cluster.c(3012): proxy_cluster_trans DECLINED (null) uri: (null) unparsed_uri: /helloworld;jsessionid=blablabla [Mon Nov 17 15:40:01 2014] [error] [client 127.0.0.1] File does not exist: /apache/htdocs/helloworld;jsessionid=blablabla [Mon Nov 17 15:40:03 2014] [debug] mod_manager.c(1907): manager_trans STATUS (/) {code} So we can't even get a "/context;jsessionid=..." request to proxy from httpd to JBoss through mod_cluster. Session data and servlet mappings don't enter the equation. > 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)

10 years, 1 month

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 commented on MODCLUSTER-443: ----------------------------------------- I'm able to reproduce the customer issue consistently with the latest versions. Extra debug logs were showing that find_node_context_host includes the ;jsessionid in the context that it searches for on the balancer: {code} [Mon Nov 17 15:40:01 2014] [debug] mod_proxy_cluster.c(2948): proxy_cluster_trans for 0 (null) (null) uri: /helloworld;jsessionid=blablabla args: (null) unparsed_uri: /helloworld;jsessionid=blablabla [Mon Nov 17 15:40:01 2014] [debug] mod_proxy_cluster.c(2769): cluster: balancer://mycluster Found value blablabla for stickysession JSESSIONID|jsessionid [Mon Nov 17 15:40:01 2014] [debug] mod_proxy_cluster.c(2769): cluster: balancer://mycluster Found value blablabla for stickysession JSESSIONID|jsessionid [Mon Nov 17 15:40:01 2014] [debug] mod_proxy_cluster.c(1943): find_node_context_host: /helloworld;jsessionid=blablabla node: 1 vhost: 1 context: /helloworld [Mon Nov 17 15:40:01 2014] [debug] mod_proxy_cluster.c(3012): proxy_cluster_trans DECLINED (null) uri: (null) unparsed_uri: /helloworld;jsessionid=blablabla [Mon Nov 17 15:40:01 2014] [error] [client 127.0.0.1] File does not exist: /apache/htdocs/helloworld;jsessionid=blablabla [Mon Nov 17 15:40:03 2014] [debug] mod_manager.c(1907): manager_trans STATUS (/) {code} So we can't even get a "/context;jsessionid=..." request to proxy from httpd to JBoss through mod_cluster. Session data and servlet mappings don't enter the equation. > 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)

10 years, 1 month

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 commented on MODCLUSTER-443: ------------------------------------------- O.K., I amended the test and IMHO this is no bug in proxy, but it's a wrong servlet url mapping setup. The following url works perfectly: {{http://192.168.122.172:8080/tses;jsessionid=Qq7acr8AUL+212-o9bDcgtTJ.jboss-eap-6.4}} Returning always the same session data: {code} <ul> <li>Name: jj.test.com</li> <li>Address: 192.168.122.172</li> <li>JSESSIONID: Qq7acr8AUL+212-o9bDcgtTJ.jboss-eap-6.4</li> </ul> {code} Provided one has this mapping (note url pattern): {code} <welcome-file-list> <welcome-file>session.jsp</welcome-file> </welcome-file-list> <servlet> <servlet-name>Hello</servlet-name> <jsp-file>/session.jsp</jsp-file> </servlet> <servlet-mapping> <servlet-name>Hello</servlet-name> <url-pattern>/*</url-pattern> </servlet-mapping> {code} What am I missing here? > 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)

10 years, 1 month

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 commented on MODCLUSTER-443: ------------------------------------------- Hmm, now I see I guess: While I have {{clusterbench/session;jsessionid=something}}, which is context/servlet;jsessionid=, the user is experiencing problems with the actual {{clusterbench;jsessionid=something}}, i.e. context;jsessionid= I'll give it a shot and enhance the aforementioned test case then... > 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)

10 years, 1 month

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 commented on MODCLUSTER-443: ------------------------------------------- Guys, this is weird. I have a test like this and it passes all right with mod_cluster 1.2.9.Final: https://gist.github.com/Karm/8432a95db8d75ba0d269#file-context_delimiter_... WDYT? IMHO the user mentioned on the linked Bugzilla has an old mod_cluster. > 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)

10 years, 1 month

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