We're updating the issue view to help you get more done. 

Rest API and Multi-node Hazelcast cluster - Delete Room not propagated to other nodes

Description

This is a bug in the REST API's delete MUC Room service, when Hazelcast clustering is enabled, and there is more than one Openfire/Hazelcast node in the cluster.

The failure happens when a MUCRoom is deleted via REST. It will be deleted on node which received, but it will still exist on the other nodes of the openfire cluster.

In the case of deleting a room, with multi-node clustering enabled, sending RoomRemovedEvent to the other cluster nodes will resolve the issue.

Environment

None

Acceptance Test - Entry

None

Activity

Show:
David B Harrison
April 27, 2018, 6:22 AM
Edited
David B Harrison
April 27, 2018, 5:24 PM

Pull request was merged. I'm going to resolve this issue

Fixed

Assignee

David B Harrison

Reporter

David B Harrison

Labels

Expected Effort

None

Components

Fix versions

Affects versions

Priority

Major
Configure