-
I took me a while to find out cause of this issue and it appears that it was caused by the fact that we closed XMPP stream just after parsing </stream:stream> but before processing received packets just before </stream:stream>. If in this not processed packets was packet then this NPE occured when they were processed after stream being closed.
As this premature close of stream could lead also to other packets not being processed properly, I delayed stream close to be done after packets are processed by @ClientConnectionManager@. I'm not sure, if this will not cause stream to not be closed properly due premature close of TCP connection by XMPP client.
Type |
Bug
|
Priority |
Normal
|
Assignee | |
RedmineID |
2626
|
Spent time |
0
|
Issue Votes (0)
Watchers (0)
This was triggered by massive concurrent connection/disconnection tests while trying to reproduce the issue described here: https://projects.tigase.org/boards/4/topics/4029