ejabberd - Comments for "Getting dropped from remote s2s chat servers"

First try to replicate the problem: failed

mfoss — Tue, 05 Sep 2006 10:49:03 +0000

I did my own test, but I couldn't experience the problem:

Server 1: My own small (only one user registered), ejabberd SVN, Erlang R11B-0, TLS enabled on S2S.
Server 2: jabber.ru, I created a dummy chatroom for only two participants.
Client 1: Psi 0.10. Logged on Server 1, a dummy account without contacts. It joins the dummy chatroom on Server 2.
Client 2: Tkabber 0.9.9. Logged on a dummy account on jabber.org. Joins the dummy chatroom too.

So, I login client1 and client2, and join both to the chatroom. I opened the Raw XML window of Psi to verify the client 1 did not send or receive any packet from the chatroom. I disabled autoaway on both clients. I hope no single xmpp package was sent between server 1 and server 2 once both clients joined the same chatroom.

I waited 94 minutes of inactivity (no chatting, no presence changes...), and client 1 was not disconnected from the chatroom.

I couldn't replicate the problem. If you indicate what exact version of ejabberd and Erlang you are using, I could try again.

Not a client issue

synx — Tue, 05 Sep 2006 02:09:35 +0000

I have confirmed the same problem happens on tkabber and gaim, but only for chat servers remote to my own ejabberd server. This is the situation:

1) I sign on as two JIDs, one for gaim and one for tkabber
2) I join both of them into test@conference.jabber.org
3) I allow myself to go idle for a half hour or so
4) I try to send a message to the chat room
-- replies with I'm not authorized to send messages to chat rooms I'm not a member of
5) I change my status or status message in either JID
-- the automatic scrollback gets sent to me again, as if I joined the room

I'd like to note that when I changed my status in tkabber, it sent the scrollback to the tkabber JID, but not the gaim one. When I changed my status first in gaim, the opposite occurred. If I did this weird "re-entry" of a room in one chat client with one JID, then the other JID did not experience problems, even though it had been idle just as long. It didn't matter which chat client it was, whatever the first one I used "re-entered" the room, and the other one experienced no odd behavior.

Since the only thing in common between changing my status in gaim, with JID #1, and changing it in tkabber, with JID #2, is that both JIDs are running from the same ejabberd server, I think I can conclusively say it is [u]not[/u] a client issue.

Yup...

synx — Sun, 03 Sep 2006 15:31:34 +0000

Gaim never was that robust in regards to group chats, but I think tkabber had problems too. Let me check that and I'll get back to thread. (The problem only comes up when I'm idle for a while)

Looks like a client issue.

sander — Sat, 02 Sep 2006 16:49:58 +0000

Looks like a client issue. Did you already tried with other clients?

--
sander