[ejabberd] Strange MUC behavior

Sylvain Niles sylvain.niles at gmail.com
Wed Apr 13 22:31:43 MSD 2011


That's been my conclusion too.. I'm currently writing a module
mod_muc_reaper that will force clients on surviving nodes to reconnect if a
node in the cluster goes down. It's not graceful but it does get everything
to a consistent state. Would love to hear if anyone has a better idea...
-Sylvain


On Wed, Apr 13, 2011 at 11:19 AM, Daniel Dormont
<dan at greywallsoftware.com>wrote:

> I've been looking into this recently and can summarize with this statement:
> indvidual MUC rooms are not clustered. If the room is not pre-configured as
> persistent, it will live on the node of whichever user creates it. If that
> node is shut down cleanly, the room is destroyed and other users in the room
> will get a message to that effect. If that node is shut down uncleanly, the
> other node will remove the MUC from the database, but it will not know who
> the participants of that MUC were. So User2 will not be automatically
> notified. If User2 tries to send messages *after* User1 has already
> recreated the MUC they will fail because User2 is not an occupant of the
> (recreated) MUC.
>
> The only solution I know of is to have User2 rejoin, but I'm interested in
> others' inputs also.
>
> dan
>
> On Apr 12, 2011, at 7:22 PM, Sylvain Niles wrote:
>
> PS: We're running ejabberd 2.1.6, thanks!
>
>
> On Tue, Apr 12, 2011 at 4:21 PM, Sylvain Niles <sylvain.niles at gmail.com>wrote:
>
>> We're seeing some strange MUC behavior:
>>
>> server1 & server2 = example.com
>> User1 logs into server1 and creates mucroom1
>> User2 logs into server2 and joins mucroom1
>> server1 goes down
>> User1 reconnects to server2 and rejoins mucroom1 (works fine
>> User2 types chat messages into mucroom1 but they show up as system
>> messages to User1 and User2 sees no new messages for mucroom1
>> User2 rejoins room and behavior returns to normal.
>>
>> I would expect User2 to get some sort of error or a forced rejoin to the
>> MUC instead of having to manually detect that a problem is occurring and
>> rejoining. Any ideas on why this happens and how we can fix?
>>
>> Thanks,
>> Sylvain
>>
>>
> _______________________________________________
> ejabberd mailing list
> ejabberd at jabber.ru
> http://lists.jabber.ru/mailman/listinfo/ejabberd
>
>
>
> _______________________________________________
> ejabberd mailing list
> ejabberd at jabber.ru
> http://lists.jabber.ru/mailman/listinfo/ejabberd
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jabber.ru/pipermail/ejabberd/attachments/20110413/1ad940bc/attachment.html>


More information about the ejabberd mailing list