Project

General

Profile

Bug #7431

Ad-hoc command requests to the other resource of the same user are not always delivered.

Added by Andrzej Wójcik IoT 1 CloudTigaseTeam 10 months ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Database:
n/a
Applicable version:
git/master
Source Code Disclaimer:

Description

Sometimes, ad-hoc requests send from one resource of the user to the other resource of the same user are not delivered - are just dropped with NoConnectionIdException in the server logs.

Associated revisions

Revision 76733ac2 (diff)
Added by Andrzej Wójcik IoT 1 CloudTigaseTeam 10 months ago

#7431: fixed issue with routing adhoc requests between cluster nodes for two resources of the same user but hosted on different cluster nodes

History

#1 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam 10 months ago

  • Status changed from New to In QA
  • % Done changed from 0 to 100

It related to the bug in routing implementation in JabberIqCommand while it was working fine in PacketDefaultHandler so I used an instance of PacketDefaultHandler in JabberIqCommand to have single <iq/> ad-hoc command handling implementation which works.

#2 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam 10 months ago

  • Status changed from In QA to Closed

Also available in: Atom PDF