[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-97) httpd should remove workers who crashed

[Michal Babacek (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Babacek closed MODCLUSTER-97.
------------------------------------



Closing. Clean-up.
At least one of the following applies:

  * the issue has been thoroughly tested as a part of one of the current releases
or
  * it hasn't occurred in ~2 years
or
  * it's utterly harmless

> httpd should remove workers who crashed
> ---------------------------------------
>
>                 Key: MODCLUSTER-97
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-97
>             Project: mod_cluster
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.0.1.GA
>            Reporter: Bela Ban
>            Assignee: Jean-Frederic Clere
>             Fix For: 1.1.0.Beta1
>
>
> When worker W crashes, httpd will not remove it from its worker tables and still try to send requests to W. 
> We should implement something like ping_mode=I (interval), ping_timeout and connection_ping_interval in mod_jk [1].
> It should work as follows:
> - W crashes
> - httpd waits for connection_ping_interval of idle time, then starts checking the connection to W every ping_timeout seconds (or ms)
> - When the connection to W is broken, httpd should remove W from its worker table and stop the connection checker
> - When (if !) W is started again, mod-cluster will register it again with httpd
> The configuration above should be done entirely on the AS side, e.g. in HAModClusterConfig. maybe we can find just 1 attribute rather than 3.
> [1] http://tomcat.apache.org/connectors-doc/reference/workers.html



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)