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

[Aaron Ogburn (JIRA)]

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

Aaron Ogburn commented on MODCLUSTER-376:
-----------------------------------------

Build from attached patch file:

https://brewweb.devel.redhat.com//buildinfo?buildID=314749
                
> 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
>    Affects Versions: 1.0.10
>         Environment: -JBoss Enterprise Web Server 1.0.2
> -mod_cluster 1.0.10.GA_CP04
> -Red Hat Enterprise Linux 5
>            Reporter: Aaron Ogburn
>            Assignee: Jean-Frederic Clere
>
> 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 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