I think we have managed to overcome this in a develoment machine changing the values directly in database. We are convinced this is some bug related with cache, because the rooms are still on database.
I´m not sure this will work in production(linux machine) because it seems it needs a reboot and we didn´t do it yet. In dev machine(Windows ) it didn´t disappear.
Try this in DB, table of mucroom, find fields creationDate and modificationDate, and change to a future time. This seems to do the trick.After this rebbot and check in admin area of openfire, under rooms properties if the date is to the future.
I still didn´t get what format date is on this tables (select from_unixtime(‘xxx’) doesn´t work), so try to change the first 5 to a 7…it will cheng the date to 204x… It´s stupid I Know…but I have to do what I can since this bug is here to stay, and nobody is taking care of openfire…