does ejabberd handle the case where a user is unexpectedly disconnected?
that means: the disconnected user didnt have the chance to send an "unavailable" presence message, the ejabberd "detected" it somehow and notified the other relevant users.
the XMPP IM and Presence document mentions it as a "MUST" operation but the ejabberd doesnt seem to do it.
thanks
Yonatan
Seems fixed in SVN
Yes, I remember seeing this problem. However, I use ejabberd svn version now and I can't reproduce it, maybe it's now solved.
I kill the client with a SIGKILL or SIGSEGV, and ejabberd immediately closes the session and sends updated presences to his contacts.
have you tried with version
have you tried with version 2.0.1 and its reproducible?
Test with kill -9 is senseless
Hi!
If you kill an applikation with kill -9 linux itself sends a TCP - RST (Reset) paket so the ejabberd is informed. But the real problem is: "What is if the network connection breaks and no TCP - RST paket can be send.
I tested with the jabber installation from GMX (a modified ejabberd, Domain: jabber.gmx.net). If you kill oyure network connection, then youre account is shown for a really long time as online. So this bug is still not closed.
This issue exist even with
This issue exist even with ejabberd 2.0.1 source version, I'm trying to get solved by setting linux tcp keepalive time very short interval (one minute), i.e., if client disconnect abruptly (such us power down or internet down) the ejabberd server able to get to know in one minute interval and able to release the client connection, I could able to confirm using admin interface. But same is not working if client is in session or conference room and if internet or power down, ejabberd is not able to release the client connection, it looks strange to me...I'm still working on this problem if there are any update will get shared immediately