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

mod_proxy timeout setting is not set correctly from nodeTimeout (JBoss) or ProxyTimeout (httpd) configuration in mod_cluster ---------------------------------------------------------------------------------------------------------------------------- Key: MODCLUSTER-145 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-145 Project: mod_cluster Issue Type: Bug 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 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 is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira