[JBoss JIRA] (MODCLUSTER-359) stickysession not working with httpd-2.4.6 / mod_cluster-1.2.5.Final
by Marco Danti (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-359?page=com.atlassian.jira.pl... ]
Marco Danti updated MODCLUSTER-359:
-----------------------------------
Summary: stickysession not working with httpd-2.4.6 / mod_cluster-1.2.5.Final (was: httpd crashes and stickysession problems)
> 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>
> 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.
--
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
10 years, 7 months
[JBoss JIRA] (MODCLUSTER-359) httpd crashes and stickysession problems
by Marco Danti (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-359?page=com.atlassian.jira.pl... ]
Marco Danti updated MODCLUSTER-359:
-----------------------------------
Steps to Reproduce: See description (was: Try described configuration and deploy any test/demo application that makes use of the web session.
On each application invocation from a remote client, I see that the request is routed alternatively to both JBoss servers.)
> httpd crashes and stickysession problems
> ----------------------------------------
>
> 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>
> 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.
--
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
10 years, 7 months
[JBoss JIRA] (MODCLUSTER-359) httpd crashes and stickysession problems
by Marco Danti (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-359?page=com.atlassian.jira.pl... ]
Marco Danti updated MODCLUSTER-359:
-----------------------------------
Summary: httpd crashes and stickysession problems (was: stickysession not working with httpd-2.4.6 / mod_cluster-1.2.5.Final)
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>
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.
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.
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 and this is what happens:
- 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.
> httpd crashes and stickysession problems
> ----------------------------------------
>
> 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>
> 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.
--
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
10 years, 7 months
[JBoss JIRA] (MODCLUSTER-359) stickysession not working with httpd-2.4.6 / mod_cluster-1.2.5.Final
by Marco Danti (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-359?page=com.atlassian.jira.pl... ]
Marco Danti updated MODCLUSTER-359:
-----------------------------------
Fix Version/s: (was: 1.3.0.Alpha1)
(was: 1.2.6.Final)
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.
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 and this is what happens:
- 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.
was:
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.
> 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.
> 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 and this is what happens:
> - 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.
--
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
10 years, 7 months
[JBoss JIRA] (MODCLUSTER-359) stickysession not working with httpd-2.4.6 / mod_cluster-1.2.5.Final
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-359?page=com.atlassian.jira.pl... ]
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
10 years, 7 months
[JBoss JIRA] (MODCLUSTER-359) stickysession not working with httpd-2.4.6 / mod_cluster-1.2.5.Final
by Marco Danti (JIRA)
Marco Danti created MODCLUSTER-359:
--------------------------------------
Summary: 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
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
10 years, 7 months
[JBoss JIRA] (MODCLUSTER-358) demo in master branch does not compile on JDK6
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-358?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-358:
--------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/modcluster/mod_cluster/pull/42
b0cb3f5a43ec42847d51b4303b1a9968abb12c02 in https://github.com/rhusar/mod_cluster/tree/REBASE
> demo in master branch does not compile on JDK6
> ----------------------------------------------
>
> Key: MODCLUSTER-358
> URL: https://issues.jboss.org/browse/MODCLUSTER-358
> Project: mod_cluster
> Issue Type: Bug
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 1.3.0.Alpha1
>
>
> [ERROR] COMPILATION ERROR :
> [INFO] -------------------------------------------------------------
> [ERROR] /home/rhusar/git/mod_cluster/demo/client/src/main/java/org/jboss/modcluster/demo/client/ModClusterDemo.java:[933,90] type javax.swing.ListCellRenderer does not take parameters
> [ERROR] /home/rhusar/git/mod_cluster/demo/client/src/main/java/org/jboss/modcluster/demo/client/ModClusterDemo.java:[937,59] type javax.swing.JList does not take parameters
> [ERROR] /home/rhusar/git/mod_cluster/demo/client/src/main/java/org/jboss/modcluster/demo/client/ModClusterDemo.java:[504,23] type javax.swing.JComboBox does not take parameters
> [ERROR] /home/rhusar/git/mod_cluster/demo/client/src/main/java/org/jboss/modcluster/demo/client/ModClusterDemo.java:[504,82] type javax.swing.JComboBox does not take parameters
> [ERROR] /home/rhusar/git/mod_cluster/demo/client/src/main/java/org/jboss/modcluster/demo/client/ModClusterDemo.java:[936,8] method does not override or implement a method from a supertype
> [INFO] 5 errors
--
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
10 years, 7 months
[JBoss JIRA] (MODCLUSTER-358) demo in master branch does not compile on JDK6
by Radoslav Husar (JIRA)
Radoslav Husar created MODCLUSTER-358:
-----------------------------------------
Summary: demo in master branch does not compile on JDK6
Key: MODCLUSTER-358
URL: https://issues.jboss.org/browse/MODCLUSTER-358
Project: mod_cluster
Issue Type: Bug
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Fix For: 1.3.0.Alpha1
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /home/rhusar/git/mod_cluster/demo/client/src/main/java/org/jboss/modcluster/demo/client/ModClusterDemo.java:[933,90] type javax.swing.ListCellRenderer does not take parameters
[ERROR] /home/rhusar/git/mod_cluster/demo/client/src/main/java/org/jboss/modcluster/demo/client/ModClusterDemo.java:[937,59] type javax.swing.JList does not take parameters
[ERROR] /home/rhusar/git/mod_cluster/demo/client/src/main/java/org/jboss/modcluster/demo/client/ModClusterDemo.java:[504,23] type javax.swing.JComboBox does not take parameters
[ERROR] /home/rhusar/git/mod_cluster/demo/client/src/main/java/org/jboss/modcluster/demo/client/ModClusterDemo.java:[504,82] type javax.swing.JComboBox does not take parameters
[ERROR] /home/rhusar/git/mod_cluster/demo/client/src/main/java/org/jboss/modcluster/demo/client/ModClusterDemo.java:[936,8] method does not override or implement a method from a supertype
[INFO] 5 errors
--
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
10 years, 7 months