[JBoss JIRA] (MODCLUSTER-359) stickysession not working with httpd-2.4.6 / mod_cluster-1.2.5.Final

Thursday, 3 October 2013

    [
https://issues.jboss.org/browse/MODCLUSTER-359?page=com.atlassian.jira.pl...
] 

Marco Danti commented on MODCLUSTER-359:
----------------------------------------

This is weird because it is in contrast with the documentation at
http://docs.jboss.org/mod_cluster/1.2.0/html_single/#proxy, where it says that
'sticky-session' default value is TRUE.

Up to now, I had the following configuration:

            <mod-cluster-config advertise-socket="modcluster"
advertise-security-key="secret" connector="ajp">

If I try:
            <mod-cluster-config advertise-socket="modcluster"
sticky-session="true" advertise-security-key="secret"
connector="ajp">

it makes no difference whatsoever (request is always routed alternatively to both jboss
servers); it seems that sticky-session is not considered at all

However, if I try
            <mod-cluster-config advertise-socket="modcluster"
sticky-session-force="true" advertise-security-key="secret"
connector="ajp">

then the sticky session behaviour is correct (the request is always routed to the same
server), which may be ok as a workaround but makes no sense because sticky-session-force
purpose seems to be completely different.

These last tests were done using mod_cluster-1.2.6.Final on both AS-7.2.0.Final and
Httpd-2.4.6

...
 stickysession not working with httpd-2.4.6 / mod_cluster-1.2.5.Final

 ---------------------------------------------------------------------

                 Key: MODCLUSTER-359
                 URL: https://issues.jboss.org/browse/MODCLUSTER-359
             Project: mod_cluster
          Issue Type: Bug
    Affects Versions: 1.2.5.Final, 1.2.6.Final
         Environment: OS. SLES-11-SP1 x86_64
            Reporter: Marco Danti
            Assignee: Jean-Frederic Clere
              Labels: httpd, mod_cluster, stickysession
         Attachments: MODCLUSTER-359-debug-info.tar.gz, tses.war

 Setup: HTTPD configured as reverse proxy / load balancer for two instances of
JBOSS-AS-7.2.0.Final running in HA configuration on two separate nodes.
 Consider the following configuration (defined inside my virtual hosts)

 <Proxy balancer://mycluster>
   ProxySet stickysession=JSESSIONID|jsessionid
 </Proxy>
 On httpd-2.2.24 / mod_cluster-1.2.0.Final it shows the following behaviour:
 - 'stickysession' is working as expected
 After upgrading to httpd-2.4.6/mod_cluster-1.2.5.Final things are worse:
 - 'stickysession' is ignored and any client request gets dispatched alternatively

    to each one of the two JBoss servers (exactly as if lbmethod=byrequest were defined)
 As a final consideration, I read in the docs that stickysession should be enabled by
default in mod_cluster anyway, but that is not the case for me. 
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009