Unexpected packet on cluster connection - customized
Added 8 months ago
We are running a Tigase XMPP server 7.1.0 with ACS 2.3.1
The cluster is consisting of 4 nodes spread 2x2 over 2 data-centers.
We are using custom plugins and scripts to limit communication.
But we are experiencing issues where clients across the cluster do not see each other, outputting this message:
/opt/tigase/logs/tigase.log.1:2018-05-28 18:18:38.945 [out_49-cl-comp] ClusterConnectionManager.processOutPacket() FINER: Unexpected packet on cluster connection: from=sess-man@server-01, to=ws2s@server-03/server-03_5290_client-01_56874, DATA=<presence from="firstname.lastname@example.org/00:00:00:00:00:03" xmlns="jabber:client"><data>%7B%22name%22%3A%22Living%20Room%22%2C%22ip%22%3A%22client-02%22%2C%22type%22%3A%22MOTOROLA_4%22%2C%22typeDetail%22%3A%22VIP1113%22%2C%22multiscreen%22%3Afalse%2C%22recordingHost%22%3Afalse%2C%22castingReceiver%22%3Atrue%7D</data></presence>, SIZE=335, XMLNS=jabber:client, PRIORITY=PRESENCE, PERMISSION=NONE, TYPE=null
This primarily happens when we are changing IPs on the client-01 device ( roaming ), and we suspect it's some sort of sticky-ness issue?
Note: I have changed the Mac,IP and other identifying information.
Added by Artur Hefczyc 8 months ago
I am afraid it is impossible to assist you with this problem without a proper investigation. Especially that you have some custom code. The clustering logic depends on specific XMPP data, therefore if you have custom plugins which limit communication, it is possible that they affect clustering functioning.
If you would like us to help you to resolve the issue, I suggest you contact our team on a private channel to discuss what would be the best way to work together on investigation.
Added by Anonymous 8 months ago
Thank you for your quick response Artur!
How do we go about a proper investigation? Pricing, arrangement and such?
We do not have any issues with sharing the code. And i agree with you
that we might be causing this by our custom plug-in and might want it
reviewed - since it is from 2012.
The message was posted in case you have seen the issue before and that
we could correlate with others.
On 2018-05-28 21:09, email@example.com wrote: