[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-145) mod_proxy timeout setting is not set correctly from nodeTimeout (JBoss) or ProxyTimeout (httpd) configuration in mod_cluster

[Michal Babacek (JIRA)]

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

Michal Babacek closed MODCLUSTER-145.
-------------------------------------



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

> mod_proxy timeout setting is not set correctly from nodeTimeout (JBoss) or ProxyTimeout (httpd) configuration in mod_cluster
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MODCLUSTER-145
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-145
>             Project: mod_cluster
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.1.0.CR1
>         Environment: CentOS5.4 Xen host 
> JBossAS 5.1.0.GA running on jdk6 backend,  on 2 hosts. mod_cluster configured in clustered mode.
> httpd-2.2.3-31.el5.centos.4 with manual mod_cluster configuration on frontend server host
> multicast disabled at a network layer
> jgroups configured with TCP transport and PING/gossip discovery
>            Reporter: Brett Cave
>            Assignee: Jean-Frederic Clere
>              Labels: failover, mod_cluster, nodeTimeout
>
> If 1 backend AS process is killed, the frontend proxy still connects clients to the dead node. The node is removed from mod_proxy after 5 minutes. All requests are directed to the dead node.
> mod-cluster manager status shows the node as status=NOTOK.
> client connections to this node result in 503 errors.
> After backend is removed from configuration after 5 minutes, requests to httpd still result in 503 errors as request is routed to the unavailable node. Even new sessions from different hosts try to get routed to the dead node, resulting in 503 errors.
> The note on www.jboss.org/mod_cluster/java/properties.html:
> When nodeTimeout is not defined, the ProxyTimeout directive Proxy is used. If ProxyTimeout is not defined the server timeout (Timeout) is used (default 300 seconds). nodeTimeout, ProxyTimeout or Timeout is set at the socket level.
> As per the configuration below, nodeTimeout is set in the Listener configuration. In addition to that, ProxyTimeout has been enabled and disabled on the httpd server. Timeout is configured with default of 120.



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