will try tcp keepalive solution, but chat client support is odd

aklemm — Wed, 31 Jan 2007 19:19:36 +0000

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!

It's in the FAQ

legoscia — Wed, 31 Jan 2007 10:23:26 +0000

See How to close sessions for crashed clients.

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.

ejabberd - Comments for "ejabberd not releasing sessions/connections"

will try tcp keepalive solution, but chat client support is odd

It's in the FAQ