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

[Radoslav Husar (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar updated MODCLUSTER-359:
--------------------------------------

    Fix Version/s: 1.3.0.Alpha1
                   1.2.6.Final

    
> 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
>         Environment: OS. SLES-11-SP1 x86_64
>            Reporter: Marco Danti
>            Assignee: Jean-Frederic Clere
>              Labels: httpd, mod_cluster, stickysession
>             Fix For: 1.3.0.Alpha1, 1.2.6.Final
>
>
> Setup: HTTPD configured as reverse proxy / load balancer for two instances of JBOSS-AS-7.2.0.Final on separate nodes.
> In the following configuration (defined inside my virtual hosts), the stickysession directive worked as expected using httpd-2.2.24/mod_cluster-1.2.0.Final.
>  
> <Proxy balancer://mycluster>
>   BalancerMember ajp://stw-1:7009/ route=stw-1
>   BalancerMember ajp://stw-2:7009/ route=stw-2
>   ProxySet stickysession=JSESSIONID|jsessionid
> </Proxy>
> After upgrading to httpd-2.4.6/mod_cluster-1.2.5.Final however, it does not work any longer: 'stickysession' is ignored, and any request gets dispatched alternatively to each one of my two JBOSS-AS-7.2.0 instances running in HA mode on two different nodes (exactly as if lbmethod=byrequest were defined)
> I read in the docs that stickysession should be enabled by default in mod_cluster anyway, but that is not the case for me.
> Please note that I get the same problem either with or without the two BalancerMember directives.

--
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