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.
I think second issue with the same room names was fixed in a one of your patches from
Yes wroot, Guus and I decided to split the 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.
Done. I've also changed affect version back to 3.6.4.
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.
After the successfully tests of wroot and a secound review I committed the patch to r11194.