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

[Jean-Frederic Clere (JIRA)]

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

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