Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

System property for MUC disabling doesnt work

Description

There is a system property (xmpp.muc.enabled) documented in http://www.igniterealtime.org/community/docs/DOC-1061 but it doesn't seem to work. This could be a major issue for some companies, if they want their users just to have single conversations and not to do group chats.

Environment

None

Activity

Show:

Guenther Niess March 18, 2010 at 3:42 PM

Committed a patch to revision 11666.

wroot March 13, 2010 at 3:33 PM

Well, if i have 10 MUC services and just want to disable whole MUC, then it better to have one system property. Of course it would be nice also to be able to disable one service by one. As about deleting domains. Well, this is a bug i think and should be fixed probably? If it is disabled it shouldn't be loaded.

Guenther Niess March 13, 2010 at 2:43 PM

Oh and since 3.6.0 if you want to disable the MUC service permanently you should better delete all service domains via admin console. Because if the service is only disabled it will be loaded into the memory anyway.

Guenther Niess March 13, 2010 at 2:34 PM

Since you have to specify the enabled property within the ofMucServiceProp table for each MUC service. Maybe we should use the old xmpp.muc.enabled property as default value (if no domain specific enabled property is set)?

wroot March 11, 2010 at 7:34 PM

yes, twice, and i still can join rooms and create new

Fixed

Details

Assignee

Reporter

Fix versions

Affects versions

Priority

Created March 11, 2010 at 5:57 PM
Updated March 18, 2010 at 3:42 PM
Resolved March 18, 2010 at 3:42 PM