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

[Radoslav Husar (JIRA)]

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

Radoslav Husar commented on MODCLUSTER-344:
-------------------------------------------

That's the point of the Jira: all distributions of mod_cluster that we officially support seem to already support HTTP/1.1 (correct me if I am wrong) and we should have defaults that best fit our customers and majority of the userbase.
                
> 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