-
It related to the bug in routing implementation in
JabberIqCommandwhile it was working fine inPacketDefaultHandlerso I used an instance ofPacketDefaultHandlerinJabberIqCommandto have single<iq/>ad-hoc command handling implementation which works.
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| RedmineID |
7431
|
| Version |
tigase-server-8.0.0
|
| Spent time |
0
|
Issue Votes (0)
Watchers (0)
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
NoConnectionIdExceptionin the server logs.