I could see preAuthenticatedSession in LocalSessionManager class with thousands of sessions not removed. Even it contains sessions with CLOSED state. Is this expected?
Please note: I have upgraded netty in my setup to 4.1.108-Final (which was the fix for other memory issue in 4.8.1)
Interesting! I’ve never ran into this. Can you share how you found this issue, and what made you think that upgrading Netty would resolve it?
Hi Guus
Netty has nothing to with this issue. As we know 4.8.1 has already memory issue and fix is there in 4.8.2 ([OF-2818] - Ignite Realtime Jira).
Added the note to clarify that, it is not same issue we are hitting here.
We got this problem in out load setup, where around 3k of user login. Got the out of memory not able to create native thread issue. Then when I checked heapdump with before OOM and after - two memory snapshots, first one has preAuthenticatedSession around 3k (6MB) values and later has 48k values (190MB of retained heap)
Thanks
From a cursory look through the code, I’m not seeing an immediate problem. Can you share exactly how this problem is reproduced? Do the clients that connect finish authentication? Do the entries in preAuthenticatedSession (eventually) disappear, when timeouts occur?