Hi,
When a user exits (worst-case, say they reboot a machine without logging out of their Jabber client) a Jabber session, ejabberd shows them still connected to the server for long periods of time afterwards. In these cases, they are not able to log in elsewhere. I'm going to 'solve' this (I think) with the [{max_user_sessions, 6}] configuration.
However, most of my users are always going to connect with the /Gaim resource so that may be a problem.
Any ideas how to get ejabberd to release connections faster or at all?
Thanks so much.
It's in the FAQ
See .
However, it is actually a good thing if users always use the same resource, since a new session with resource X will terminate any old session with that resource.
will try tcp keepalive solution, but chat client support is odd
Thanks for the tip! That just may fix up the most important part of my problem.
Secondary piece remains:
I used '{access, max_user_sessions, [{6, all}]}.' hoping users could reconnect from elsewhere without or without specifying a different resource and ejabberd would terminate their old sessions. So far I've only seen this actually work with the Gossip jabber client. Gaim, Exodus, Pandion, Gajim; none of these allow a user to login when they have a session opened elsewhwere regardless of the resource they specify.
Ideas? Client suggestions are welcome, and ejabberd solutions are most welcome. Basically users are locked out of the jabber server if they've forgot to logout *or* if their machine crashed etc.
Thanks again!
ak