You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have deployed an instance of MIM and an external service that uses the HTTP admin API to query the list of sessions and find out which users are currently online, and I noticed that the API reports sessions that are not in use since a long time.
It seems that when the client disconnect abruptly, the session remains on the server until it's restarted (I presume this is because sessions are stored in mnesia, and they would remain forever if I was using redis ?). I am using JWT auth with a TTL of 1 hour, and the sessions remain after the expiry of the JWT.
Is this the expected behaviour? I would expect that the session be destroyed when the server realises the connection is broken, for example when trying to deliver a received message (N.B.: I didn't enable mod_ping).
Can I change this behaviour by configuration, and give a timeout to stale sessions?
Is there a better way to find out if a user is online from the admin API?
The text was updated successfully, but these errors were encountered:
MongooseIM version: 6.2.1
Installed from: Docker
I have deployed an instance of MIM and an external service that uses the HTTP admin API to query the list of sessions and find out which users are currently online, and I noticed that the API reports sessions that are not in use since a long time.
It seems that when the client disconnect abruptly, the session remains on the server until it's restarted (I presume this is because sessions are stored in mnesia, and they would remain forever if I was using redis ?). I am using JWT auth with a TTL of 1 hour, and the sessions remain after the expiry of the JWT.
The text was updated successfully, but these errors were encountered: