powered by Jive Software

MUC Presence variance w/ Hazelcast, different hosts and JAXL

I’m starting to experiemnt with JAXL, so I’m not sure if this is an OF bug or a JAXL issue. I pretty much took to their example bot code and got it connected to my OF environment - Two nodes, Hazelcast for clustering. The JAXL app basically connects to Openfire, then joins a persistent MUC that has one user in it. The user and the JAXL client do not have any roster information.

If my JAXL app connects to get the same OF instance as the user I get what I believe to be ‘correct’ presence information about the user who is in the MUC: http://pastebin.com/M2xXqnBX

If JAXL conncets to the other host, but the user stays where they are, I get screwy presence about the user that doesn’t include MUC information: http://pastebin.com/SCfdbRyd

Like I said, I’m unsure if it’s a JAXL issue or Openfire, but since it seems to be the Hazelcast part in the middle that influences the presence information I figured it was worth checking to see if anyone else had the same problem.

OK - looks like an issue with MUC presence when running with clustering enabled. Opened OF-670 to track.

Tom - Looks like you were unable to reproduce this problem? We’re seeing it pretty frequently in production, and I can reproduce it with two pidgin clients in our dev environment, or a pidgin and a JAXL client.

Is there any additional information I can provide to aid in troubleshooting? Our dev environment is pretty simple - Just two systems running OF 3.8.2 w/ Hazelcast and Oracle db backend.


This issue is different one as OF-670, these issue can be fixed by change class UpdatePresence.java

public UpdatePresence(LocalMUCRoom room, Presence presence, String nickname) {


this.presence = presence;

// Change this

** this.presence.setFrom(presence.getTo());**

this.nickname = nickname;