Open terrypacker opened 5 years ago
From what I could gather in testing this the PingPong tracker was failing to send the message and closing the connection but the session was not yet in the Set. I've changed the order so that the session is in the Set prior to calling super.afterConnectionEstablished().
This is the commit for the changes:
I have seen Mango end up with an extra web socket session that is in the MultiSessionWebSocketHnadler.session list. To reproduce login to Mango, terminate it externally then rebuild/deploy the api module and start Mango. Let the page redirect you to the login page and then upon login you will see the following, resulting in a session being left in the list but closed.