Can someone help

dandormont — Thu, 24 Feb 2011 02:34:13 +0000

Does anyone have any ideas on this issue? I understand that auto-archiving to the database of persistent MUC history is a feature that doesn't currently exist. That's ok. But I'm still hoping there's a way my client does not have to explicitly rejoin the room when the node *that* client is connected to is still live. thanks

I researched this a little

dandormont — Fri, 18 Feb 2011 16:47:58 +0000

I researched this a little more on my own and found that as long as I set the muc tables to ram and disk copy on "second" then at least the configuration of the room carries over, but there are two things I'd like to see if I can get past:

The client has to explicitly rejoin the MUC in order for it to be properly recreated on the clustered server. Since the client is still logged in, I was hoping that the MUC would at least appear to be still live and the client would not get the "shutdown" message I mentioned above.
It appears that the history of the MUC is not clustered. Is there any way to achieve that, short of hacking mod_muc (which I'm hesitant to do since I don't know Erlang)?

Any thoughts would be appreciated.

ejabberd - Comments for "Persistent MUC not failing over to clustered node"

Can someone help

I researched this a little