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

Michal Babacek (JIRA) jira-events at lists.jboss.org
Tue May 28 12:09:54 EDT 2013


    [ https://issues.jboss.org/browse/MODCLUSTER-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777535#comment-12777535 ] 

Michal Babacek commented on MODCLUSTER-344:
-------------------------------------------

Hmm, which server does not support HTTP 1.1? Tomcat6, Tomcat7, AS5, AS6, AS7 and WildFly all support it by default I guess.

Regarding http_handle_cping_cpong and HTTPS connector: I created [MODCLUSTER-345] and I am going to try to make it work...looks like one would need something like {{RequestHeader set Front-End-Https "On"}} or even {{CreateBalancers 1}} and a custom {{ProxyPass}}  :(
                
> 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


More information about the mod_cluster-issues mailing list