https://issues.apache.org/bugzilla/show_bug.cgi?id=57532
--- Comment #4 from andrew jardine <andrew.jard...@jardineworks.com> --- I have tried this with 2 nodes all the way up to 5 nodes -- all configured the same, all the same results. The odd thing is that it only seems to affect sessions that are marked as Primary on the node that is being shut down. For example. Node A Node B session 1 (primary) session 1 session 2 session 2 (primary) session 3 session 3 (primary) session 4 (primary) session 4 session 5 (primary) session 5 If at this point I shutdown Node B, then session 2 and session 3 on Node A will be destroyed leaving me with - Node A Node B session 1 (primary) session 4 (primary) session 5 (primary) ... but all nodes that were not primary do not appear to be sending the "SESSION EXPIRE" message to the cluster. I'll try to get that thread dump for you when I get a bit of breathing room at work. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
