|
Andrzej Wójcik (Tigase) opened 1 decade ago
|
|
Ghostbuster in MUC Component uses XEP-0199 to check resource availability. MUC sends to JID with resource and it expect to stanza will be delivered to exactly this resource or returned with error (for example 'recipient-unavailable'). |
|
Let's do it as one of the first things for version 5.2.0 |
|
|
This ticket is to fix/correct a default packet delivery in the Tigase. For some specific packet types the logic is implemented in a separate plugin which needs to be reviewed to ensure correct packet delivery. |
|
|
Applied in changeset tigase-server|commit:43ffa897dd3668646ca3a02a38b18d64ed709a96. |
|
|
Applied in changeset heliostech:commit:43ffa897dd3668646ca3a02a38b18d64ed709a96. |
| Type |
Bug
|
| Priority |
Critical
|
| Assignee | |
| RedmineID |
688
|
| Version |
tigase-server-5.2.0
|
| Estimation |
16h
|
Related
Issue Votes (0)
Watchers (0)
When there are two or more connections to two or more different cluster nodes authenticated as same user but using different resources stanzas are sent to connections which are having highest priority or which full jid matches destination address.
example:
user@tigase.im/tigase-1 is connected to node orange
user@tigase.im/tigase-2 is connected to node blue
test@tigase.org/tigase is sending stanza to user@tigase.im/tigase-1 but it will be delivered to user@tigase.im/tigase-1 and user@tigase.im/tigase-2 as each of them is "best destination" for each of cluster node. This matching connection is done by getResourceConnection method in XMPPSession class.
I think that stanza sent to full jid should be delivered
onlyto connection which resource matches resource of full jid.