[JBoss JIRA] (MODCLUSTER-364) mod_cluster and mod_proxy : keeping session
by Michal Karm (Jira)
[ https://issues.jboss.org/browse/MODCLUSTER-364?page=com.atlassian.jira.pl... ]
Michal Karm commented on MODCLUSTER-364:
----------------------------------------
Leaving the topic.
If [~jfclere] is interested; he might find someone to look into it or close it. It is likely outdated though.
> mod_cluster and mod_proxy : keeping session
> -------------------------------------------
>
> Key: MODCLUSTER-364
> URL: https://issues.jboss.org/browse/MODCLUSTER-364
> Project: mod_cluster
> Issue Type: Bug
> Components: Native (httpd modules)
> Reporter: Michal Karm
> Assignee: Jean-Frederic Clere
> Priority: Major
>
> Why this config:
> {noformat}
> ProxyPassMatch ^/app/static/ !
> ProxyPass /app balancer://qacluster stickysession=JSESSIONID|jsessionid nofailover=on
> ProxyPass / !
> ProxyPassReverse /app balancer://qacluster
> ProxyPassReverseCookieDomain / /app/
> ProxyPassReverseCookiePath / /app/
> ProxyPreserveHost on
> {noformat}
> does not keep the same session? I keep getting new sessions while hitting F5 with {{http://server:6666/app/clusterbench/requestinfo/}}
> *TODO:* Investigate whether it is a configuration error or mod_clutser's incompatibility.
> According to this [blog post|http://www.brandonchecketts.com/archives/use-proxypassreversecookied...], it should be trivial :-(
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (MODCLUSTER-364) mod_cluster and mod_proxy : keeping session
by Michal Karm (Jira)
[ https://issues.jboss.org/browse/MODCLUSTER-364?page=com.atlassian.jira.pl... ]
Michal Karm reassigned MODCLUSTER-364:
--------------------------------------
Assignee: Jean-Frederic Clere (was: Michal Karm)
> mod_cluster and mod_proxy : keeping session
> -------------------------------------------
>
> Key: MODCLUSTER-364
> URL: https://issues.jboss.org/browse/MODCLUSTER-364
> Project: mod_cluster
> Issue Type: Bug
> Components: Native (httpd modules)
> Reporter: Michal Karm
> Assignee: Jean-Frederic Clere
> Priority: Major
>
> Why this config:
> {noformat}
> ProxyPassMatch ^/app/static/ !
> ProxyPass /app balancer://qacluster stickysession=JSESSIONID|jsessionid nofailover=on
> ProxyPass / !
> ProxyPassReverse /app balancer://qacluster
> ProxyPassReverseCookieDomain / /app/
> ProxyPassReverseCookiePath / /app/
> ProxyPreserveHost on
> {noformat}
> does not keep the same session? I keep getting new sessions while hitting F5 with {{http://server:6666/app/clusterbench/requestinfo/}}
> *TODO:* Investigate whether it is a configuration error or mod_clutser's incompatibility.
> According to this [blog post|http://www.brandonchecketts.com/archives/use-proxypassreversecookied...], it should be trivial :-(
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (MODCLUSTER-425) The timeout specified has expired: proxy: AJP: cping/cpong failed, ajp_ilink_receive() can't receive header
by Michal Karm (Jira)
[ https://issues.jboss.org/browse/MODCLUSTER-425?page=com.atlassian.jira.pl... ]
Michal Karm commented on MODCLUSTER-425:
----------------------------------------
Leaving the topic.
If [~jfclere] is interested; he might find someone to look into it or close it.
> The timeout specified has expired: proxy: AJP: cping/cpong failed,ajp_ilink_receive() can't receive header
> ----------------------------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-425
> URL: https://issues.jboss.org/browse/MODCLUSTER-425
> Project: mod_cluster
> Issue Type: Bug
> Components: Native (httpd modules)
> Affects Versions: 1.2.6.Final, 1.2.9.Final
> Environment: Confirmed RHEL6 x86_64
> Reporter: Michal Karm
> Assignee: Jean-Frederic Clere
> Priority: Major
>
> mod_cluster balancer used in front of GateIn Portal, after certain warm-up time, starts to show:
> {code}
> [debug] proxy_util.c(2200): proxy: connected / to perf13:8009
> [debug] mod_proxy_cluster.c(1384): proxy_cluster_try_pingpong: connected to backend
> [debug] mod_proxy_cluster.c(1108): ajp_cping_cpong: Done
> [debug] proxy_util.c(2036): proxy: ajp: has released connection for (perf13)
> [debug] proxy_util.c(2018): proxy: ajp: has acquired connection for (perf12)
> [debug] proxy_util.c(2074): proxy: connecting ajp://perf12:8009/ to perf12:8009
> [debug] proxy_util.c(2200): proxy: connected / to perf12:8009
> [debug] proxy_util.c(2451): proxy: ajp: fam 2 socket created to connect to perf12
> [debug] mod_proxy_cluster.c(1384): proxy_cluster_try_pingpong: connected to backend
> [debug] mod_proxy_cluster.c(1108): ajp_cping_cpong: Done
> [debug] proxy_util.c(2036): proxy: ajp: has released connection for (perf12)
> [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
> [error] ajp_handle_cping_cpong: ajp_ilink_receive failed
> [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12)
> [debug] proxy_util.c(2018): proxy: ajp: has acquired connection for (perf12)
> [debug] proxy_util.c(2074): proxy: connecting ajp://perf12:8009/ to perf12:8009
> [debug] proxy_util.c(2200): proxy: connected / to perf12:8009
> [debug] mod_proxy_cluster.c(1384): proxy_cluster_try_pingpong: connected to backend
> [debug] mod_proxy_cluster.c(1108): ajp_cping_cpong: Done
> [debug] proxy_util.c(2036): proxy: ajp: has released connection for (perf12)
> [debug] proxy_util.c(2018): proxy: ajp: has acquired connection for (perf13)
> [debug] proxy_util.c(2074): proxy: connecting ajp://perf13:8009/ to perf13:8009
> [debug] proxy_util.c(2200): proxy: connected / to perf13:8009
> [debug] mod_proxy_cluster.c(1384): proxy_cluster_try_pingpong: connected to backend
> [debug] mod_proxy_cluster.c(1108): ajp_cping_cpong: Done
> [debug] proxy_util.c(2036): proxy: ajp: has released connection for (perf13)
> [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
> [error] ajp_handle_cping_cpong: ajp_ilink_receive failed
> [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12)
> [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
> [error] ajp_handle_cping_cpong: ajp_ilink_receive failed
> [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12)
> [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
> [error] ajp_handle_cping_cpong: ajp_ilink_receive failed
> [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12)
> [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
> [error] ajp_handle_cping_cpong: ajp_ilink_receive failed
> [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12)
> [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
> [error] ajp_handle_cping_cpong: ajp_ilink_receive failed
> [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12)
> [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
> {code}
> Investigation is going on...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (MODCLUSTER-425) The timeout specified has expired: proxy: AJP: cping/cpong failed, ajp_ilink_receive() can't receive header
by Michal Karm (Jira)
[ https://issues.jboss.org/browse/MODCLUSTER-425?page=com.atlassian.jira.pl... ]
Michal Karm reassigned MODCLUSTER-425:
--------------------------------------
Assignee: Jean-Frederic Clere (was: Michal Karm)
> The timeout specified has expired: proxy: AJP: cping/cpong failed,ajp_ilink_receive() can't receive header
> ----------------------------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-425
> URL: https://issues.jboss.org/browse/MODCLUSTER-425
> Project: mod_cluster
> Issue Type: Bug
> Components: Native (httpd modules)
> Affects Versions: 1.2.6.Final, 1.2.9.Final
> Environment: Confirmed RHEL6 x86_64
> Reporter: Michal Karm
> Assignee: Jean-Frederic Clere
> Priority: Major
>
> mod_cluster balancer used in front of GateIn Portal, after certain warm-up time, starts to show:
> {code}
> [debug] proxy_util.c(2200): proxy: connected / to perf13:8009
> [debug] mod_proxy_cluster.c(1384): proxy_cluster_try_pingpong: connected to backend
> [debug] mod_proxy_cluster.c(1108): ajp_cping_cpong: Done
> [debug] proxy_util.c(2036): proxy: ajp: has released connection for (perf13)
> [debug] proxy_util.c(2018): proxy: ajp: has acquired connection for (perf12)
> [debug] proxy_util.c(2074): proxy: connecting ajp://perf12:8009/ to perf12:8009
> [debug] proxy_util.c(2200): proxy: connected / to perf12:8009
> [debug] proxy_util.c(2451): proxy: ajp: fam 2 socket created to connect to perf12
> [debug] mod_proxy_cluster.c(1384): proxy_cluster_try_pingpong: connected to backend
> [debug] mod_proxy_cluster.c(1108): ajp_cping_cpong: Done
> [debug] proxy_util.c(2036): proxy: ajp: has released connection for (perf12)
> [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
> [error] ajp_handle_cping_cpong: ajp_ilink_receive failed
> [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12)
> [debug] proxy_util.c(2018): proxy: ajp: has acquired connection for (perf12)
> [debug] proxy_util.c(2074): proxy: connecting ajp://perf12:8009/ to perf12:8009
> [debug] proxy_util.c(2200): proxy: connected / to perf12:8009
> [debug] mod_proxy_cluster.c(1384): proxy_cluster_try_pingpong: connected to backend
> [debug] mod_proxy_cluster.c(1108): ajp_cping_cpong: Done
> [debug] proxy_util.c(2036): proxy: ajp: has released connection for (perf12)
> [debug] proxy_util.c(2018): proxy: ajp: has acquired connection for (perf13)
> [debug] proxy_util.c(2074): proxy: connecting ajp://perf13:8009/ to perf13:8009
> [debug] proxy_util.c(2200): proxy: connected / to perf13:8009
> [debug] mod_proxy_cluster.c(1384): proxy_cluster_try_pingpong: connected to backend
> [debug] mod_proxy_cluster.c(1108): ajp_cping_cpong: Done
> [debug] proxy_util.c(2036): proxy: ajp: has released connection for (perf13)
> [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
> [error] ajp_handle_cping_cpong: ajp_ilink_receive failed
> [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12)
> [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
> [error] ajp_handle_cping_cpong: ajp_ilink_receive failed
> [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12)
> [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
> [error] ajp_handle_cping_cpong: ajp_ilink_receive failed
> [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12)
> [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
> [error] ajp_handle_cping_cpong: ajp_ilink_receive failed
> [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12)
> [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
> [error] ajp_handle_cping_cpong: ajp_ilink_receive failed
> [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12)
> [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
> {code}
> Investigation is going on...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months