Creating new room on cluster generates exception on one node
I cannot consistently reproduce this issue, but I have seen it at least once at ignite's server (running 4.6.2 b61bce3).
I attempted to use the Inverse plugin (v7.0.4 release 1) to create a new chatroom in a clustered Openfire instance. I did this by filling out the address for a not-yet-existing chatroom in Converse's "add a new groupchat" dialog (hidden behind the + icon above the roster).
One one node (I believe it's the one where the client creating the room was connected to), the room seems to have been created as expected. On the other node, an exception was logged. The end result was that the admin panels of both nodes displayed the room, but on only on the 'local' node, the room has an occupant (me). On the other node, the room seems empty.
Logged on the local node:
Logged on the remote node:
As I wrote, I can't reproduce this at will. My suspicion is that there is a race between two asynchronous cluster events ("room created" and "occupant added").