Issues
- MUC members variable on remote node doesn't seem to be updated after an invite is transmittedJM-1265Resolved issue: JM-1265Gaston Dombiak
- Add support for enabling/disabling the pubsub serviceJM-1262Resolved issue: JM-1262Gaston Dombiak
- Allow to set default max number of users when creating new roomsJM-1260Resolved issue: JM-1260Gaston Dombiak
- Add JID to room search resultsJM-1259Resolved issue: JM-1259Gaston Dombiak
- Fix small memory leak in Multi User ChatJM-1251Resolved issue: JM-1251Daniel Henninger
- Add ability to set VM options from config file in DebianJM-1250Resolved issue: JM-1250Daniel Henninger
- Debian postinstall should be checking to make sure openfire group existsJM-1249Resolved issue: JM-1249Daniel Henninger
- RPM throwing warnings about ci and jivedevJM-1248Resolved issue: JM-1248Daniel Henninger
- Can't delete an avatar using LDAPJM-1240Resolved issue: JM-1240Gaston Dombiak
9 of 9
MUC members variable on remote node doesn't seem to be updated after an invite is transmitted
Fixed
Description
Environment
None
Created February 7, 2008 at 4:13 AM
Updated February 7, 2008 at 8:59 AM
Resolved February 7, 2008 at 8:59 AM
Activity
Show:
Something odd happens with regards to MUC rooms. If you create a MUC room, and send someone else an invitation, the user is not able to join the MUC room if that user is on a remote Openfire node. Disabling the 'members only' configuration option for the MUC is a workaround for the problem.
Initial investigation by Gato revealed that the member variable that of the MUC isn't updated over the cluster. LocalMUCRoom#addMember seems to be the cause of the problems.