Ad-hoc command requests to the other resource of the same user are not always delivered.
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.
#1 Updated by Andrzej Wójcik 12 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
JabberIqCommand to have single
<iq/> ad-hoc command handling implementation which works.