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

Thu Oct 3 02:52:02 EDT 2013

    [ https://issues.jboss.org/browse/MODCLUSTER-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12809098#comment-12809098 ] 

Jean-Frederic Clere commented on MODCLUSTER-359:
------------------------------------------------

A quick looks shows: (httpd-2.4.6_mpm_prefork_modcluster-1.2.6_error_log)
JVMRoute=stw-1&Host=172.16.0.133&Maxattempts=1&Port=7009&StickySessionForce=No&Type=ajp&ping=10
there must be something wrong in your tests.

> 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