[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-376) multiple workers with the same id following a tomcat crash/kill

[Jean-Frederic Clere (JIRA)]

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

Jean-Frederic Clere updated MODCLUSTER-376:
-------------------------------------------
    Git Pull Request: https://github.com/modcluster/mod_cluster/pull/189, https://github.com/modcluster/mod_proxy_cluster/pull/12  (was: https://github.com/modcluster/mod_cluster/pull/189)


> multiple workers with the same id following a tomcat crash/kill
> ---------------------------------------------------------------
>
>                 Key: MODCLUSTER-376
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-376
>             Project: mod_cluster
>          Issue Type: Bug
>          Components: Native (httpd modules)
>    Affects Versions: 1.0.10, 1.2.11.Final
>         Environment: -JBoss Enterprise Web Server 1.0.2
> -mod_cluster 1.0.10.GA_CP04
> -Red Hat Enterprise Linux 5
>            Reporter: Aaron Ogburn
>            Assignee: Michal Karm Babacek
>             Fix For: 1.2.13.Final
>
>         Attachments: 131122.patch
>
>
> Following a kill or crash of tomcat, multiple workers are seen for a single id when a new tomcat node reconnects and reuses the id from the previously crashed worker.
> The STATUS's ping check sees the old crashed worker first for the id and so pings the wrong destination.  Thus the ping fails, and load factor is not applied.  The persistent -1 load state leads to 503s.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)