Skip to:

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

Loading and creating rooms with multiple conferences services fails

Description

There are issues with new multiple conferences services introduced in 3.6.0.:

  • Sometimes when creating new server it copies permanent room from previous service.

  • When trying to create room with same ID of the room in other service it throws an error, that such room already exists, but still lets you to create such room.

Environment

None

Attachments

1
  • 01 Jul 2009, 04:22 PM

Activity

Show:

Guenther Niess August 22, 2009 at 1:32 AM

After the successfully tests of wroot and a secound review I committed the patch to r11194.

Guenther Niess July 10, 2009 at 8:37 PM

Just a view words to explain the relation between the described bugs and the createAndLoadRoom.patch.
If someone tries to create or access a room which isn't present in the cache then the MultiUserChatServiceImpl#getChatRoom(String roomName, JID userjid) will be called. Here it tries the MUCPersistenceManager#loadFromDB method which doesn't respect the current service (it tries to load the room from all available services). This causes the described behavior of the bug and is fixed by the createAndLoadRoom patch.

wroot July 1, 2009 at 6:12 PM

Done. I've also changed affect version back to 3.6.4.

Guenther Niess July 1, 2009 at 4:58 PM

Yes wroot, Guus and I decided to split the https://igniterealtime.atlassian.net/browse/OF-27#icft=OF-27 into smaller issues. This allows a better discussion on the different bugs. Maybe you can delete the outdated createAndLoadRoom and repairDB patch from OF-27.

wroot July 1, 2009 at 4:24 PM

I think second issue with the same room names was fixed in a one of your patches from https://igniterealtime.atlassian.net/browse/OF-27#icft=OF-27

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created July 1, 2009 at 4:13 PM
Updated February 1, 2010 at 3:27 AM
Resolved August 22, 2009 at 1:32 AM