[
https://issues.jboss.org/browse/MODCLUSTER-359?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere updated MODCLUSTER-359:
-------------------------------------------
Comment: was deleted
(was: Please, how do i get the updated version? I don't really understand the
difference between the 1.2.? versions and the MOD_CLUSTER_1_0_10_GA_CPxxx versions. Up to
now I just went along by getting the .zip from 1.2.something but now I don't know what
to do.)
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
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