May 2013 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-339) "proxy: DNS lookup failure" with IPv6 on Solaris

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-339?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on MODCLUSTER-339: ---------------------------------------------------- Jean-frederic Clere <jclere(a)redhat.com> made a comment on [bug 963723|https://bugzilla.redhat.com/show_bug.cgi?id=963723] Not in EAP6.1 = not EWS 2.0.1 = unknown bug. > "proxy: DNS lookup failure" with IPv6 on Solaris > ------------------------------------------------ > > Key: MODCLUSTER-339 > URL: https://issues.jboss.org/browse/MODCLUSTER-339 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.3.Final, 1.2.4.Final > Environment: Solaris 10 x86, Solaris 11 x86, Solaris 11 SPARC > Reporter: Michal Babacek > Assignee: Jean-Frederic Clere > Priority: Critical > Labels: ipv6 > Fix For: 1.2.5.Final > > Attachments: access_log-mod_cluster, error_log-mod_cluster, error_log-mod_cluster-RHEL, error_log-proxypass, http.conf > > > h2. Failure with mod_cluster > Having the following setting: > {code:title=mod_cluster.conf|borderStyle=solid|borderColor=#ccc| titleBGColor=#F7D6C1} > LoadModule slotmem_module modules/mod_slotmem.so > LoadModule manager_module modules/mod_manager.so > LoadModule proxy_cluster_module modules/mod_proxy_cluster.so > LoadModule advertise_module modules/mod_advertise.so > MemManagerFile "/tmp/mod_cluster-eap6/jboss-ews-2.0/var/cache/mod_cluster" > ServerName [2620:52:0:105f::ffff:50]:2080 > <IfModule manager_module> > Listen [2620:52:0:105f::ffff:50]:6666 > LogLevel debug > <VirtualHost [2620:52:0:105f::ffff:50]:6666> > ServerName [2620:52:0:105f::ffff:50]:6666 > <Directory /> > Order deny,allow > Deny from all > Allow from all > </Directory> > KeepAliveTimeout 60 > MaxKeepAliveRequests 0 > ServerAdvertise on > AdvertiseFrequency 5 > ManagerBalancerName qacluster > AdvertiseGroup [ff01::7]:23964 > EnableMCPMReceive > <Location /mcm> > SetHandler mod_cluster-manager > Order deny,allow > Deny from all > Allow from all > </Location> > </VirtualHost> > </IfModule> > {code} > I get a weird {{proxy: DNS lookup failure}} as soon as worker sends {{CONFIGURE}}}: > {code:title=access_log|borderStyle=solid|borderColor=#ccc| titleBGColor=#F7D6C1} > 2620:52:0:105f::ffff:50 - - [16/May/2013:08:37:24 -0400] "INFO / HTTP/1.1" 200 - "-" "ClusterListener/1.0" > 2620:52:0:105f::ffff:50 - - [16/May/2013:08:37:24 -0400] "CONFIG / HTTP/1.1" 200 - "-" "ClusterListener/1.0" > 2620:52:0:105f::ffff:50 - - [16/May/2013:08:37:24 -0400] "STATUS / HTTP/1.1" 200 64 "-" "ClusterListener/1.0" > ... > {code} > {code:title=error_log|borderStyle=solid|borderColor=#ccc| titleBGColor=#F7D6C1} > ... > [Thu May 16 08:37:24 2013] [debug] mod_manager.c(1923): manager_trans INFO (/) > [Thu May 16 08:37:24 2013] [debug] mod_manager.c(2598): manager_handler INFO (/) processing: "" > [Thu May 16 08:37:24 2013] [debug] mod_manager.c(2647): manager_handler INFO OK > [Thu May 16 08:37:24 2013] [debug] mod_manager.c(1923): manager_trans CONFIG (/) > [Thu May 16 08:37:24 2013] [debug] mod_manager.c(2598): manager_handler CONFIG (/) processing: "JVMRoute=jboss-eap-6.1&Host=%5B2620%3A52%3A0%3A105f%3A0%3A0%3Affff%3A50%252%5D&Maxattempts=1&Port=8009&StickySessionForce=No&Type=ajp&ping=10" > [Thu May 16 08:37:24 2013] [debug] mod_manager.c(2647): manager_handler CONFIG OK > [Thu May 16 08:37:24 2013] [debug] mod_manager.c(1923): manager_trans STATUS (/) > [Thu May 16 08:37:24 2013] [debug] mod_manager.c(2598): manager_handler STATUS (/) processing: "JVMRoute=jboss-eap-6.1&Load=100" > [Thu May 16 08:37:24 2013] [debug] mod_manager.c(1638): Processing STATUS > [Thu May 16 08:37:24 2013] [debug] mod_proxy_cluster.c(655): add_balancer_node: Create balancer balancer://qacluster > [Thu May 16 08:37:24 2013] [debug] mod_proxy_cluster.c(426): Created: worker for ajp://[2620:52:0:105f:0:0:ffff:50%2]:8009 > [Thu May 16 08:37:24 2013] [debug] mod_proxy_cluster.c(532): proxy: initialized worker 1 in child 16847 for (2620:52:0:105f:0:0:ffff:50%2) min=0 max=25 smax=25 > [Thu May 16 08:37:24 2013] [debug] mod_proxy_cluster.c(601): Created: worker for ajp://[2620:52:0:105f:0:0:ffff:50%2]:8009 1 (status): 1 > [Thu May 16 08:37:24 2013] [debug] proxy_util.c(2011): proxy: ajp: has acquired connection for (2620:52:0:105f:0:0:ffff:50%2) > [Thu May 16 08:37:24 2013] [debug] proxy_util.c(2067): proxy: connecting ajp://[2620:52:0:105f:0:0:ffff:50%2]:8009/ to 2620:52:0:105f:0:0:ffff:50%2:8009 > [Thu May 16 08:37:24 2013] [error] [client 2620:52:0:105f::ffff:50] proxy: DNS lookup failure for: 2620:52:0:105f:0:0:ffff:50%2 returned by / > [Thu May 16 08:37:24 2013] [debug] proxy_util.c(2029): proxy: ajp: has released connection for (2620:52:0:105f:0:0:ffff:50%2) > ... > {code} > An attempt to access the mod_cluster manager console yields an unpleasant {{NOTOK}} (obviously, we have All workers are in error state...): > {code} > curl -g [2620:52:0:105f::ffff:50]:6666/mcm > ... > <h1> Node jboss-eap-6.1 (ajp://[2620:52:0:105f:0:0:ffff:50%2]:8009): </h1> > <a href="/mcm?nonce=1bddeeea-f9d5-eeea-ee5b-e3a5e3c0a965&Cmd=ENABLE-APP&Range=NODE&JVMRoute=jboss-eap-6.1">Enable Contexts</a> <a href="/mcm?nonce=1bddeeea-f9d5-eeea-ee5b-e3a5e3c0a965&Cmd=DISABLE-APP&Range=NODE&JVMRoute=jboss-eap-6.1">Disable Contexts</a><br/> > Balancer: qacluster,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 26,Ttl: 60000000,Status: NOTOK,Elected: 0,Read: 0,Transferred: 0,Connected: 0,Load: -1 > {code} > You might take a look at the logs: [^error_log-mod_cluster], [^access_log-mod_cluster]. > h2. ProxyPass itself works just fine > On the other hand, when I had tried this: > {code:title=proxypass.conf|borderStyle=solid|borderColor=#ccc| titleBGColor=#F7D6C1} > LoadModule proxy_ajp_module modules/mod_proxy_ajp.so > ServerName [2620:52:0:105f::ffff:50]:2080 > Listen [2620:52:0:105f::ffff:50]:6666 > LogLevel debug > <VirtualHost [2620:52:0:105f::ffff:50]:6666> > ServerName [2620:52:0:105f::ffff:50]:6666 > ProxyPass / ajp://[2620:52:0:105f:0:0:ffff:50]:8009/ > ProxyPassReverse / ajp://[2620:52:0:105f:0:0:ffff:50]:8009/ > <Directory /> > Order deny,allow > Deny from all > Allow from all > </Directory> > </VirtualHost> > {code} > I received: > {code:title=error_log|borderStyle=solid|borderColor=#ccc| titleBGColor=#F7D6C1} > ... > [Thu May 16 08:29:00 2013] [debug] mod_proxy_ajp.c(45): proxy: AJP: canonicalising URL //[2620:52:0:105f:0:0:ffff:50]:8009/ > [Thu May 16 08:29:00 2013] [debug] proxy_util.c(1506): [client 2620:52:0:105f::ffff:50] proxy: ajp: found worker ajp://[2620:52:0:105f:0:0:ffff:50]:8009/ for ajp://[2620:52:0:105f:0:0:ffff:50]:8009/ > [Thu May 16 08:29:00 2013] [debug] mod_proxy.c(1020): Running scheme ajp handler (attempt 0) > [Thu May 16 08:29:00 2013] [debug] mod_proxy_http.c(1963): proxy: HTTP: declining URL ajp://[2620:52:0:105f:0:0:ffff:50]:8009/ > [Thu May 16 08:29:00 2013] [debug] mod_proxy_ajp.c(681): proxy: AJP: serving URL ajp://[2620:52:0:105f:0:0:ffff:50]:8009/ > [Thu May 16 08:29:00 2013] [debug] proxy_util.c(2011): proxy: AJP: has acquired connection for (2620:52:0:105f:0:0:ffff:50) > [Thu May 16 08:29:00 2013] [debug] proxy_util.c(2067): proxy: connecting ajp://[2620:52:0:105f:0:0:ffff:50]:8009/ to 2620:52:0:105f:0:0:ffff:50:8009 > [Thu May 16 08:29:00 2013] [debug] proxy_util.c(2193): proxy: connected / to 2620:52:0:105f:0:0:ffff:50:8009 > [Thu May 16 08:29:00 2013] [debug] proxy_util.c(2444): proxy: AJP: fam 26 socket created to connect to 2620:52:0:105f:0:0:ffff:50 > ... > {code} > And from the client's side, it worked: > {{curl -g [2620:52:0:105f::ffff:50]:6666/}} brought me the worker's home page (EAP's welcome in this case). > Take a look at the whole log [^error_log-proxypass]. > *Note:* The [^http.conf] was the same both for mod_cluster and for proxypass test. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-345) http_handle_cping_cpong with EnableOptions and HTTPS connector

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-345?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-345: -------------------------------------- Summary: http_handle_cping_cpong with EnableOptions and HTTPS connector (was: http_handle_cping_cpong with EnableOptions does not work) > http_handle_cping_cpong with EnableOptions and HTTPS connector > -------------------------------------------------------------- > > Key: MODCLUSTER-345 > URL: https://issues.jboss.org/browse/MODCLUSTER-345 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.3.Final, 1.2.4.Final > Reporter: Michal Babacek > Assignee: Michal Babacek > Fix For: 1.2.5.Final > > > {noformat} > [error] [client 127.0.0.1] SSL Proxy requested for 127.0.0.1:8888 but not enabled [Hint: SSLProxyEngine] > [error] proxy: https: failed to enable ssl support for 127.0.0.1:8443 (127.0.0.1) > {noformat} > {code} > MemManagerFile /home/mbabacek/EAP6/cache/mod_cluster > ServerName 127.0.0.1:8888 > <IfModule manager_module> > Listen 127.0.0.1:8888 > <VirtualHost 127.0.0.1:8888> > <Directory /> > Order deny,allow > Deny from all > Allow from all > </Directory> > ServerAdvertise on > EnableMCPMReceive > <Location /mod_cluster_manager> > SetHandler mod_cluster-manager > Order deny,allow > Deny from all > Allow from all > </Location> > > EnableOptions > > SSLEngine on > LogLevel debug > SSLCipherSuite AES128-SHA:ALL:!ADH:!LOW:!MD5:!SSLV2:!NULL > SSLVerifyDepth 10 > SSLProxyEngine On > SSLCertificateKeyFile /home/mbabacek/EAP6/certs/server.key > SSLCertificateFile /home/mbabacek/EAP6/certs/server.crt > SSLCACertificateFile /home/mbabacek/EAP6/certs/myca.crt > </VirtualHost> > </IfModule> > {code} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-345) http_handle_cping_cpong with EnableOptions does not work

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-345?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-345: -------------------------------------- Description: {noformat} [error] [client 127.0.0.1] SSL Proxy requested for 127.0.0.1:8888 but not enabled [Hint: SSLProxyEngine] [error] proxy: https: failed to enable ssl support for 127.0.0.1:8443 (127.0.0.1) {noformat} {code} MemManagerFile /home/mbabacek/EAP6/cache/mod_cluster ServerName 127.0.0.1:8888 <IfModule manager_module> Listen 127.0.0.1:8888 <VirtualHost 127.0.0.1:8888> <Directory /> Order deny,allow Deny from all Allow from all </Directory> ServerAdvertise on EnableMCPMReceive <Location /mod_cluster_manager> SetHandler mod_cluster-manager Order deny,allow Deny from all Allow from all </Location> EnableOptions SSLEngine on LogLevel debug SSLCipherSuite AES128-SHA:ALL:!ADH:!LOW:!MD5:!SSLV2:!NULL SSLVerifyDepth 10 SSLProxyEngine On SSLCertificateKeyFile /home/mbabacek/EAP6/certs/server.key SSLCertificateFile /home/mbabacek/EAP6/certs/server.crt SSLCACertificateFile /home/mbabacek/EAP6/certs/myca.crt </VirtualHost> </IfModule> {code} was: http_cping_cpong: received HTTP/1.1 405 Method Not Allowed > http_handle_cping_cpong with EnableOptions does not work > -------------------------------------------------------- > > Key: MODCLUSTER-345 > URL: https://issues.jboss.org/browse/MODCLUSTER-345 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.3.Final, 1.2.4.Final > Reporter: Michal Babacek > Assignee: Michal Babacek > Fix For: 1.2.5.Final > > > {noformat} > [error] [client 127.0.0.1] SSL Proxy requested for 127.0.0.1:8888 but not enabled [Hint: SSLProxyEngine] > [error] proxy: https: failed to enable ssl support for 127.0.0.1:8443 (127.0.0.1) > {noformat} > {code} > MemManagerFile /home/mbabacek/EAP6/cache/mod_cluster > ServerName 127.0.0.1:8888 > <IfModule manager_module> > Listen 127.0.0.1:8888 > <VirtualHost 127.0.0.1:8888> > <Directory /> > Order deny,allow > Deny from all > Allow from all > </Directory> > ServerAdvertise on > EnableMCPMReceive > <Location /mod_cluster_manager> > SetHandler mod_cluster-manager > Order deny,allow > Deny from all > Allow from all > </Location> > > EnableOptions > > SSLEngine on > LogLevel debug > SSLCipherSuite AES128-SHA:ALL:!ADH:!LOW:!MD5:!SSLV2:!NULL > SSLVerifyDepth 10 > SSLProxyEngine On > SSLCertificateKeyFile /home/mbabacek/EAP6/certs/server.key > SSLCertificateFile /home/mbabacek/EAP6/certs/server.crt > SSLCACertificateFile /home/mbabacek/EAP6/certs/myca.crt > </VirtualHost> > </IfModule> > {code} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-345) http_handle_cping_cpong with EnableOptions does not work

by Michal Babacek (JIRA)

Michal Babacek created MODCLUSTER-345: ----------------------------------------- Summary: http_handle_cping_cpong with EnableOptions does not work Key: MODCLUSTER-345 URL: https://issues.jboss.org/browse/MODCLUSTER-345 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.4.Final, 1.2.3.Final Reporter: Michal Babacek Assignee: Michal Babacek Fix For: 1.2.5.Final http_cping_cpong: received HTTP/1.1 405 Method Not Allowed -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-342) Cannot start apache

by Jose Giner (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-342?page=com.atlassian.jira.pl... ] Jose Giner commented on MODCLUSTER-342: --------------------------------------- Any solution? > Cannot start apache > ------------------- > > Key: MODCLUSTER-342 > URL: https://issues.jboss.org/browse/MODCLUSTER-342 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.1.3.Final > Environment: LPAR on AIX 7 (httpd 2.2.14) > Reporter: Jose Giner > Assignee: Jean-Frederic Clere > > Hi, > We cannot start apache. > The error_log show: > [Fri May 24 12:30:23 2013] [warn] Init: Session Cache is not configured [hint: SSLSessionCache] > [Fri May 24 12:30:23 2013] [notice] Digest: generating secret for digest authentication ... > [Fri May 24 12:30:23 2013] [notice] Digest: done > [Fri May 24 12:30:24 2013] [emerg] create_mem_host failed > Configuration Failed > Regards, -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-344) No pings when using HTTP connector in default configuration

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-344?page=com.atlassian.jira.pl... ] Jean-Frederic Clere edited comment on MODCLUSTER-344 at 5/28/13 2:47 AM: ------------------------------------------------------------------------- OPTION has been added to fix JBPAPP-9493 but OPTION is not supported by all servers that is why it is not enabled by default. was (Author: jfclere): OPTION has been added to fix JBPAPP-9493 but OPTION is not supported by all server that is why it is not enabled by default. > No pings when using HTTP connector in default configuration > ------------------------------------------------------------ > > Key: MODCLUSTER-344 > URL: https://issues.jboss.org/browse/MODCLUSTER-344 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.4.Final > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > Attachments: access_log, error_log, mod_cluster.conf > > > When integrating Undertow, I realized the servers are never removed from m_c when I am using HTTP connector to workaroung broken cping/cpong in Undertow's AJP. > One needs to configure EnableOptions to enable liveness checking, otherwise the node is never marked as NOTOK (in the larger than ping interval) until next request is received on that node and a client gets an unnecessary error. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-344) No pings when using HTTP connector in default configuration

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-344?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-344. -------------------------------------------- Resolution: Rejected > No pings when using HTTP connector in default configuration > ------------------------------------------------------------ > > Key: MODCLUSTER-344 > URL: https://issues.jboss.org/browse/MODCLUSTER-344 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.4.Final > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > Attachments: access_log, error_log, mod_cluster.conf > > > When integrating Undertow, I realized the servers are never removed from m_c when I am using HTTP connector to workaroung broken cping/cpong in Undertow's AJP. > One needs to configure EnableOptions to enable liveness checking, otherwise the node is never marked as NOTOK (in the larger than ping interval) until next request is received on that node and a client gets an unnecessary error. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-344) No pings when using HTTP connector in default configuration

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-344?page=com.atlassian.jira.pl... ] Jean-Frederic Clere edited comment on MODCLUSTER-344 at 5/28/13 2:45 AM: ------------------------------------------------------------------------- OPTION has been added to fix JBPAPP-9493 but OPTION is not supported by all server that is why it is not enabled by default. was (Author: jfclere): OPTION has been added to fix JBPAPP-9493 > No pings when using HTTP connector in default configuration > ------------------------------------------------------------ > > Key: MODCLUSTER-344 > URL: https://issues.jboss.org/browse/MODCLUSTER-344 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.4.Final > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > Attachments: access_log, error_log, mod_cluster.conf > > > When integrating Undertow, I realized the servers are never removed from m_c when I am using HTTP connector to workaroung broken cping/cpong in Undertow's AJP. > One needs to configure EnableOptions to enable liveness checking, otherwise the node is never marked as NOTOK (in the larger than ping interval) until next request is received on that node and a client gets an unnecessary error. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-344) No pings when using HTTP connector in default configuration

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-344?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-344: ------------------------------------------------ OPTION has been added to fix JBPAPP-9493 > No pings when using HTTP connector in default configuration > ------------------------------------------------------------ > > Key: MODCLUSTER-344 > URL: https://issues.jboss.org/browse/MODCLUSTER-344 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.4.Final > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > Attachments: access_log, error_log, mod_cluster.conf > > > When integrating Undertow, I realized the servers are never removed from m_c when I am using HTTP connector to workaroung broken cping/cpong in Undertow's AJP. > One needs to configure EnableOptions to enable liveness checking, otherwise the node is never marked as NOTOK (in the larger than ping interval) until next request is received on that node and a client gets an unnecessary error. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-344) No pings when using HTTP connector in default configuration

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-344?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-344: -------------------------------------- Attachment: error_log access_log mod_cluster.conf > No pings when using HTTP connector in default configuration > ------------------------------------------------------------ > > Key: MODCLUSTER-344 > URL: https://issues.jboss.org/browse/MODCLUSTER-344 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.4.Final > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > Attachments: access_log, error_log, mod_cluster.conf > > > When integrating Undertow, I realized the servers are never removed from m_c when I am using HTTP connector to workaroung broken cping/cpong in Undertow's AJP. > One needs to configure EnableOptions to enable liveness checking, otherwise the node is never marked as NOTOK (in the larger than ping interval) until next request is received on that node and a client gets an unnecessary error. -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues May 2013