[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-44) Sessions not removed from /mod_cluster-manager app on failover

[Michal Babacek (JIRA)]

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

Michal Babacek closed MODCLUSTER-44.
------------------------------------



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

> Sessions not removed from /mod_cluster-manager app on failover
> --------------------------------------------------------------
>
>                 Key: MODCLUSTER-44
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-44
>             Project: mod_cluster
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.0.0.Beta3
>            Reporter: Bela Ban
>            Assignee: Jean-Frederic Clere
>             Fix For: 1.0.0.Beta4
>
>
> When I start node1 and create 2 sessions, I see (localhost:8000/mod_cluster-manager):
> SessionIDs:
> id: DrP58P0i889C9crgfGfHQQ__.node1 route: node1
> id: PC4ET-Eeb0KJqsnuvcg0tA__.node1 route: node1
> Then I start node2 and kill node1. Sessions now fail over to node2, but http://localhost:8000/mod_cluster-manager still shows
> SessionIDs:
> id: DrP58P0i889C9crgfGfHQQ__.node1 route: node1
> id: PC4ET-Eeb0KJqsnuvcg0tA__.node1 route: node1
> id: DrP58P0i889C9crgfGfHQQ__.node2 route: node2
> id: PC4ET-Eeb0KJqsnuvcg0tA__.node2 route: node2
> I think the node1-related sessions should be removed because node1 is down !



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