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

[Marco Danti (JIRA)]

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

Marco Danti updated MODCLUSTER-359:
-----------------------------------

    Description: 
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.



  was:
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>
  BalancerMember ajp://stw-1:7009/ route=stw-1
  BalancerMember ajp://stw-2:7009/ route=stw-2
  ProxySet stickysession=JSESSIONID|jsessionid
</Proxy>

On httpd-2.2.24 / mod_cluster-1.2.0.Final it shows the following behaviour:

- if the 'BalancerMember' directives are omitted, then 'stickysession' is 
  working as expected

- if the 'BalancerMember' directives are left in place, then the httpd server 
  generates a segment fault in mod_proxy_cluster.c, in function
  "find_route_worker" at the line saying

      if (*(worker->s->route) && strcmp(worker->s->route, route) == 0) {

  because worker->s is NULL


After upgrading to httpd-2.4.6/mod_cluster-1.2.5.Final things are worse:

- if the 'BalancerMember' directives are omitted, then '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)

- if the 'BalancerMember' directives are left in place, then the httpd server 
  generates a segment fault in mod_proxy_cluster.c, in function
  "internal_find_best_byrequests" when attempting to access the variable 
  'helper' (defined as 'proxy_cluster_helper *helper') because the line

       helper = (proxy_cluster_helper *) worker->context;

   results in helper == NULL.


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.




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