October 2015 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-401) EnableOptions and SSL configuration

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-401?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on MODCLUSTER-401: ---------------------------------------------------- anrobert(a)redhat.com changed the Status of [bug 1093853|https://bugzilla.redhat.com/show_bug.cgi?id=1093853] from ASSIGNED to CLOSED > EnableOptions and SSL configuration > ----------------------------------- > > Key: MODCLUSTER-401 > URL: https://issues.jboss.org/browse/MODCLUSTER-401 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.8.Final > Environment: HP-UX Apache HTTP Server 2.2.15, RHEL Apache HTTP Server 2.2.22, perhaps platform independent... > Reporter: Michal Karm Babacek > Assignee: Jean-Frederic Clere > Fix For: 1.2.12.Final > > > As a follow up on MODCLUSTER-400 and a documentation effort for *EnableOptions* logic, I tried to add {{EnableOptions}} to the configuration so as to allow for a "cping/cpong" emulation of the famous AJP feature. > With the following {{mod_cluster.conf / httpd.conf}} (standalone-ha.xml being the same as in MODCLUSTER-400's description): > {code} > +++ > Listen 10.16.92.191:2081 > +++ > MemManagerFile "/hell/workspace/hpws22/apache/cache/mod_cluster" > ServerName 10.16.92.191:2081 > <IfModule manager_module> > Listen 10.16.92.191:8745 > LogLevel debug > <VirtualHost 10.16.92.191:8745> > ServerName 10.16.92.191:8745 > <Directory /> > Order deny,allow > Deny from all > Allow from all > </Directory> > KeepAliveTimeout 60 > MaxKeepAliveRequests 0 > ServerAdvertise on > AdvertiseFrequency 5 > ManagerBalancerName qacluster > AdvertiseGroup 224.0.3.47:23364 > EnableOptions > EnableMCPMReceive > SSLEngine on > SSLProtocol all -SSLv2 -SSLv3 > SSLCipherSuite "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH+aRSA+RC4 EECDH EDH+aRSA RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS" > SSLHonorCipherOrder on > SSLCertificateFile /vault/server.crt > SSLCertificateKeyFile /vault/server.key > SSLCACertificateFile /vault/myca.crt > SSLProxyEngine On > SSLVerifyDepth 10 > <Location /mcm> > SetHandler mod_cluster-manager > Order deny,allow > Deny from all > Allow from all > </Location> > </VirtualHost> > </IfModule> > {code} > one gets this [^hp-ux_error_log-EnableOptions.zip] log: > {code} > [debug] mod_proxy_cluster.c(1223): http_cping_cpong: received HTTP/1.1 200 OK > [debug] mod_proxy_cluster.c(1223): http_cping_cpong: received Server: Apache-Coyote/1.1 > [debug] mod_proxy_cluster.c(1223): http_cping_cpong: received Allow: GET, HEAD, POST, PUT, DELETE, TRACE, OPTIONS > [debug] mod_proxy_cluster.c(1223): http_cping_cpong: received Content-Length: 0 > [debug] mod_proxy_cluster.c(1223): http_cping_cpong: received Date: Fri, 02 May 2014 17:22:46 GMT > [debug] mod_proxy_cluster.c(1223): http_cping_cpong: received Connection: close > [debug] mod_proxy_cluster.c(1239): http_cping_cpong: Done > [debug] proxy_util.c(2047): proxy: https: has released connection for (10.16.92.191) > [debug] mod_manager.c(2666): manager_handler STATUS OK > [debug] proxy_util.c(2029): proxy: https: has acquired connection for (10.16.92.191) > [debug] proxy_util.c(2085): proxy: connecting https://10.16.92.191:8645/ to 10.16.92.191:8645 > [debug] proxy_util.c(2211): proxy: connected / to 10.16.92.191:8645 > [debug] proxy_util.c(2462): proxy: https: fam 2 socket created to connect to 10.16.92.191 > [debug] mod_proxy_cluster.c(1384): proxy_cluster_try_pingpong: connected to backend > [error] [client 10.16.92.191] SSL Proxy requested for 10.16.92.191:2081 but not enabled [Hint: SSLProxyEngine] > [error] proxy: https: failed to enable ssl support for 10.16.92.191:8645 (10.16.92.191) > [debug] proxy_util.c(2047): proxy: https: has released connection for (10.16.92.191) > {code} > Why is the JBoss EAP residing on {{10.16.92.191:8645}} trying to request SSL Proxy on the virtual host {{10.16.92.191:2081}}? The result is {{Status: NOTOK}} on mod_cluser manager console. > I tried to remove that {{10.16.92.191:2081}}, so as the {{10.16.92.191:8745}} is the only one ([^hp-ux_error_log-EnableOptions-single-vhost.zip]): > {code} > - Listen 10.16.92.191:2081 > - ServerName 10.16.92.191:2081 > {code} > The result is a funny trial to request a proxy for the boxe's actual hostname and port 80 *no one* (netstat) is even listening on: > {code} > [debug] mod_proxy_cluster.c(1223): http_cping_cpong: received HTTP/1.1 200 OK > [debug] mod_proxy_cluster.c(1223): http_cping_cpong: received Server: Apache-Coyote/1.1 > [debug] mod_proxy_cluster.c(1223): http_cping_cpong: received Allow: GET, HEAD, POST, PUT, DELETE, TRACE, OPTIONS > [debug] mod_proxy_cluster.c(1223): http_cping_cpong: received Content-Length: 0 > [debug] mod_proxy_cluster.c(1223): http_cping_cpong: received Date: Fri, 02 May 2014 17:39:33 GMT > [debug] mod_proxy_cluster.c(1223): http_cping_cpong: received Connection: close > [debug] mod_proxy_cluster.c(1239): http_cping_cpong: Done > [debug] proxy_util.c(2047): proxy: https: has released connection for (10.16.92.191) > [debug] mod_manager.c(2666): manager_handler STATUS OK > [debug] proxy_util.c(2029): proxy: https: has acquired connection for (10.16.92.191) > [debug] proxy_util.c(2085): proxy: connecting https://10.16.92.191:8645/ to 10.16.92.191:8645 > [debug] proxy_util.c(2211): proxy: connected / to 10.16.92.191:8645 > [debug] proxy_util.c(2462): proxy: https: fam 2 socket created to connect to 10.16.92.191 > [debug] mod_proxy_cluster.c(1384): proxy_cluster_try_pingpong: connected to backend > [error] [client 10.16.92.191] SSL Proxy requested for eap-perf-hpux-03.mw.lab.eng.bos.redhat.com:80 but not enabled [Hint: SSLProxyEngine] > [error] proxy: https: failed to enable ssl support for 10.16.92.191:8645 (10.16.92.191) > [debug] proxy_util.c(2047): proxy: https: has released connection for (10.16.92.191) > {code} > I tried to add: {{RequestHeader set Front-End-Https "On"}} to the configuration without any luck. > Finally, I replicated the SSL configuration *outside* the VirtualHost: > {code} > MemManagerFile "/hell/workspace/hpws22/apache/cache/mod_cluster" > Listen 10.16.92.191:2081 > ServerName 10.16.92.191:2081 > SSLEngine on > SSLProtocol all -SSLv2 -SSLv3 > SSLCipherSuite "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH+aRSA+RC4 EECDH EDH+aRSA RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !S RP !DSS" > SSLHonorCipherOrder on > SSLCertificateFile /vault/server.crt > SSLCertificateKeyFile /vault/server.key > SSLCACertificateFile /vault/myca.crt > SSLProxyEngine On > SSLVerifyDepth 10 > <IfModule manager_module> > +++ the same as above +++ > </IfModule> > {code} > This configuration fixed the aforementioned {{failed to enable ssl support}} *and* actually helped to workaround the MODCLUSTER-400: (log: [^hp-ux_error_log-EnableOptions-SSL_everywhere.zip]) > {code} > Fri, May 2, 2014 02:23:44 PM Request URI: /clusterbench/requestinfo > Headers: {host=10.16.92.191:8645, user-agent=curl/7.30.0, accept=*/*, cookie=JSESSIONID=2hC9ax9LGYDvQZtH0RXdBimf.jboss-eap-6.3-2, x-forwarded-for=10.16.92.191, x-forwarded-host=10.16.92.191:8745, x-forwarded-server=10.16.92.191, connection=Keep-Alive} > Host header: 10.16.92.191:8645 > Character encoding: null > JVM route: jboss-eap-6.3-2 > Session ID: 2hC9ax9LGYDvQZtH0RXdBimf.jboss-eap-6.3-2 > Session isNew: false > Fri, May 2, 2014 02:23:47 PM Request URI: /clusterbench/requestinfo > Headers: {host=10.16.92.191:8645, user-agent=curl/7.30.0, accept=*/*, cookie=JSESSIONID=2hC9ax9LGYDvQZtH0RXdBimf.jboss-eap-6.3-2, x-forwarded-for=10.16.92.191, x-forwarded-host=10.16.92.191:8745, x-forwarded-server=10.16.92.191, connection=Keep-Alive} > Host header: 10.16.92.191:8645 > Character encoding: null > JVM route: jboss-eap-6.3-2 > Session ID: 2hC9ax9LGYDvQZtH0RXdBimf.jboss-eap-6.3-2 > Session isNew: false > -- stop jboss-eap-6.3-2 -- (the same behavior with jvm kill) -- > Fri, May 2, 2014 02:23:50 PM Request URI: /clusterbench/requestinfo > Headers: {host=10.16.92.191:8544, user-agent=curl/7.30.0, accept=*/*, cookie=JSESSIONID=2hC9ax9LGYDvQZtH0RXdBimf.jboss-eap-6.3-2, x-forwarded-for=10.16.92.191, x-forwarded-host=10.16.92.191:8745, x-forwarded-server=10.16.92.191, connection=Keep-Alive} > Host header: 10.16.92.191:8544 > Character encoding: null > JVM route: jboss-eap-6.3 > Session ID: 2hC9ax9LGYDvQZtH0RXdBimf.jboss-eap-6.3 > Session isNew: false > Fri, May 2, 2014 02:23:53 PM Request URI: /clusterbench/requestinfo > Headers: {host=10.16.92.191:8544, user-agent=curl/7.30.0, accept=*/*, cookie=JSESSIONID=2hC9ax9LGYDvQZtH0RXdBimf.jboss-eap-6.3, x-forwarded-for=10.16.92.191, x-forwarded-host=10.16.92.191:8745, x-forwarded-server=10.16.92.191, connection=Keep-Alive} > Host header: 10.16.92.191:8544 > Character encoding: null > JVM route: jboss-eap-6.3 > Session ID: 2hC9ax9LGYDvQZtH0RXdBimf.jboss-eap-6.3 > Session isNew: false > Fri, May 2, 2014 02:23:56 PM Request URI: /clusterbench/requestinfo > Headers: {host=10.16.92.191:8544, user-agent=curl/7.30.0, accept=*/*, cookie=JSESSIONID=2hC9ax9LGYDvQZtH0RXdBimf.jboss-eap-6.3, x-forwarded-for=10.16.92.191, x-forwarded-host=10.16.92.191:8745, x-forwarded-server=10.16.92.191, connection=Keep-Alive} > Host header: 10.16.92.191:8544 > Character encoding: null > JVM route: jboss-eap-6.3 > Session ID: 2hC9ax9LGYDvQZtH0RXdBimf.jboss-eap-6.3 > Session isNew: false > {code} > Why isn't the {{10.16.92.191:8745}} enough? Is it a configuration error or a ProxyPass/SSL integration bug? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-366) code for the dynamic classpath variable in run-demo.bat

by Damien B (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-366?page=com.atlassian.jira.pl... ] Damien B commented on MODCLUSTER-366: ------------------------------------- https://github.com/modcluster/mod_cluster/pull/163 > code for the dynamic classpath variable in run-demo.bat > ------------------------------------------------------- > > Key: MODCLUSTER-366 > URL: https://issues.jboss.org/browse/MODCLUSTER-366 > Project: mod_cluster > Issue Type: Enhancement > Affects Versions: 1.2.6.Final > Reporter: Jan Häring > Assignee: Jean-Frederic Clere > Priority: Trivial > > Here is the code for the dynamic classpath variable in run-demo.bat: > @ECHO OFF & SETLOCAL EnableDelayedExpansion > set "CP=.\classes" > for %%i in (lib\*.jar) do ( > set "CP=!CP!;.\%%i" > ) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-397) StickySessions don't work for ProxyPass from unenabled context

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-397: ------------------------------------------- Fix Version/s: 1.3.2.Alpha1 > StickySessions don't work for ProxyPass from unenabled context > -------------------------------------------------------------- > > Key: MODCLUSTER-397 > URL: https://issues.jboss.org/browse/MODCLUSTER-397 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.3.2.Alpha1 > > > Sticky sessions are not maintained if you try to ProxyPass from an unenabled context to an enabled one. For example, consider JBoss with just /foo deployed and enabled via MCMP. Then try to ProxyPass / to /foo/ on httpd: > CreateBalancers 1 > ... > ProxyPass / balancer://mycluster/foo/ stickysession=JSESSIONID|jsessionid nofailover=On -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-438) WebSocket support for mod_cluster

by yi yin (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-438?page=com.atlassian.jira.pl... ] yi yin edited comment on MODCLUSTER-438 at 10/14/15 5:24 AM: ------------------------------------------------------------- [#Jean-Frederic Clere ] I am troubling about how to support http and websockt at the same time rather than how to support websocket. To support WebSocket for mod_cluster, i have to set option "EnableWsTunnel" in configuration of apache, and use http instead of ajp. However, it makes all the http to ws. The result is websockt supported but http not. Is there any way to for apache to support the two protocol ,http and ws, at the same time? was (Author: angelfall): [#Jean-Frederic Clere ] I am troubling about how to support http and websockt at the same time rather than how to support websocket. To support WebSocket for mod_cluster, i have to set option "EnableWsTunnel" in configuration of apache, and use http instead of ajp. However, it makes all the http to ws. The result is websockt supported but http not. Is there any way to for apache to support the two protocol ,http and ws, at the same time?] > WebSocket support for mod_cluster > --------------------------------- > > Key: MODCLUSTER-438 > URL: https://issues.jboss.org/browse/MODCLUSTER-438 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Michal Karm Babacek > Assignee: Jean-Frederic Clere > Fix For: Awaiting Volunteers > > > * take a look at mod_proxy_wstunnel > * mod_cluster should be able to load balance WebSocket connections to worker nodes > * consider high-availability with respect to WebSockets > Additional details TBD... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-438) WebSocket support for mod_cluster

by yi yin (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-438?page=com.atlassian.jira.pl... ] yi yin edited comment on MODCLUSTER-438 at 10/14/15 5:23 AM: ------------------------------------------------------------- [#Jean-Frederic Clere ] I am troubling about how to support http and websockt at the same time rather than how to support websocket. To support WebSocket for mod_cluster, i have to set option "EnableWsTunnel" in configuration of apache, and use http instead of ajp. However, it makes all the http to ws. The result is websockt supported but http not. Is there any way to for apache to support the two protocol ,http and ws, at the same time?] was (Author: angelfall): [#Jean-Frederic Clere I am troubling about how to support http and websockt at the same time rather than how to support websocket. To support WebSocket for mod_cluster, i have to set option "EnableWsTunnel" in configuration of apache, and use http instead of ajp. However, it makes all the http to ws. The result is websockt supported but http not. Is there any way to for apache to support the two protocol ,http and ws, at the same time?] > WebSocket support for mod_cluster > --------------------------------- > > Key: MODCLUSTER-438 > URL: https://issues.jboss.org/browse/MODCLUSTER-438 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Michal Karm Babacek > Assignee: Jean-Frederic Clere > Fix For: Awaiting Volunteers > > > * take a look at mod_proxy_wstunnel > * mod_cluster should be able to load balance WebSocket connections to worker nodes > * consider high-availability with respect to WebSockets > Additional details TBD... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-438) WebSocket support for mod_cluster

by yi yin (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-438?page=com.atlassian.jira.pl... ] yi yin edited comment on MODCLUSTER-438 at 10/14/15 5:22 AM: ------------------------------------------------------------- [#Jean-Frederic Clere I am troubling about how to support http and websockt at the same time rather than how to support websocket. To support WebSocket for mod_cluster, i have to set option "EnableWsTunnel" in configuration of apache, and use http instead of ajp. However, it makes all the http to ws. The result is websockt supported but http not. Is there any way to for apache to support the two protocol ,http and ws, at the same time?] was (Author: angelfall): Jean-Frederic Clere I am troubling about how to support http and websockt at the same time rather than how to support websocket. To support WebSocket for mod_cluster, i have to set option "EnableWsTunnel" in configuration of apache, and use http instead of ajp. However, it makes all the http to ws. The result is websockt supported but http not. Is there any way to for apache to support the two protocol ,http and ws, at the same time? > WebSocket support for mod_cluster > --------------------------------- > > Key: MODCLUSTER-438 > URL: https://issues.jboss.org/browse/MODCLUSTER-438 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Michal Karm Babacek > Assignee: Jean-Frederic Clere > Fix For: Awaiting Volunteers > > > * take a look at mod_proxy_wstunnel > * mod_cluster should be able to load balance WebSocket connections to worker nodes > * consider high-availability with respect to WebSockets > Additional details TBD... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-438) WebSocket support for mod_cluster

by yi yin (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-438?page=com.atlassian.jira.pl... ] yi yin commented on MODCLUSTER-438: ----------------------------------- Jean-Frederic Clere I am troubling about how to support http and websockt at the same time rather than how to support websocket. To support WebSocket for mod_cluster, i have to set option "EnableWsTunnel" in configuration of apache, and use http instead of ajp. However, it makes all the http to ws. The result is websockt supported but http not. Is there any way to for apache to support the two protocol ,http and ws, at the same time? > WebSocket support for mod_cluster > --------------------------------- > > Key: MODCLUSTER-438 > URL: https://issues.jboss.org/browse/MODCLUSTER-438 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Michal Karm Babacek > Assignee: Jean-Frederic Clere > Fix For: Awaiting Volunteers > > > * take a look at mod_proxy_wstunnel > * mod_cluster should be able to load balance WebSocket connections to worker nodes > * consider high-availability with respect to WebSockets > Additional details TBD... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-438) WebSocket support for mod_cluster

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-438?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-438: ------------------------------------------------ AJP doesn't support any form of upgrade protocol, you have to use http or https. > WebSocket support for mod_cluster > --------------------------------- > > Key: MODCLUSTER-438 > URL: https://issues.jboss.org/browse/MODCLUSTER-438 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Michal Karm Babacek > Assignee: Jean-Frederic Clere > Fix For: Awaiting Volunteers > > > * take a look at mod_proxy_wstunnel > * mod_cluster should be able to load balance WebSocket connections to worker nodes > * consider high-availability with respect to WebSockets > Additional details TBD... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-438) WebSocket support for mod_cluster

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-438?page=com.atlassian.jira.pl... ] Radoslav Husar edited comment on MODCLUSTER-438 at 10/12/15 11:17 AM: ---------------------------------------------------------------------- [~mbabacek] What's the status of the ws tunnel integration? Do we know, is this supported in Undertow-based implementation? was (Author: rhusar): [~mbabacek] What's the status of the ws tunnel integration? > WebSocket support for mod_cluster > --------------------------------- > > Key: MODCLUSTER-438 > URL: https://issues.jboss.org/browse/MODCLUSTER-438 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Michal Karm Babacek > Assignee: Jean-Frederic Clere > Fix For: Awaiting Volunteers > > > * take a look at mod_proxy_wstunnel > * mod_cluster should be able to load balance WebSocket connections to worker nodes > * consider high-availability with respect to WebSockets > Additional details TBD... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-438) WebSocket support for mod_cluster

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-438?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-438: ------------------------------------------- [~mbabacek] What's the status of the ws tunnel integration? > WebSocket support for mod_cluster > --------------------------------- > > Key: MODCLUSTER-438 > URL: https://issues.jboss.org/browse/MODCLUSTER-438 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Michal Karm Babacek > Assignee: Jean-Frederic Clere > Fix For: Awaiting Volunteers > > > * take a look at mod_proxy_wstunnel > * mod_cluster should be able to load balance WebSocket connections to worker nodes > * consider high-availability with respect to WebSockets > Additional details TBD... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues October 2015