|
Robert Larsen opened 1 decade ago
|
|
Does it happen with Tigase running in a cluster mode by any chance? |
|
|
It does run in cluster mode...only one server thou. Known problem? I can turn cluster mode off and see if that fixes it. |
|
|
I changed to non cluster mode by having '--cluster-mode = false' in init.properties, but it changed nothing. |
|
|
Ok, I just wanted to make sure it is not related to a cluster mode or misconfiguration of the cluster mode. In such a case I am leaving the ticket in Bartosz hands who is the MUC author. |
|
|
Since you guys took a look at our setup I have not been able to reproduce this so this was likely somehow caused by the high load or misconfigured queue limits. |
|
Hi! Would you like to test it again using latest code from branch devel, please? Few days ago I changed data structure in Room. Maybe it helps. |
|
|
Hi I'm already running with the latest and greatest from dev. branch and it's running smoothly. |
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| RedmineID |
2155
|
I'm using the latest MUC in Git:
But I'm experiencing problems with the occupants list sent out when joining a room. A client (Psi) I have had on a room for a day says the online number of occupants is 338, but I join the same room with another instance I only get between 60 and 80...after a couple of hours the two agree on the number.
I have attached a Python script I used for testing this behaviour.
I tried adding code to the MUC DiscoveryModule class so that disco#info requests would also deliver the number of occupants in the response.
This shows that there should be well over 300 users in that particular room, but you only get a small fraction of the list when actually joining.
I have tested this with Strophe.js, Psi and python-xmpp with similar results.