We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug A problem has emerged while upgrading to a new version of smack, it seems that the client sends the end of stream </stream:stream> but the server did not sends it back Full discussion with network traffic here: https://discourse.igniterealtime.org/t/smack-timeout-during-disconnect/90651/5
To Reproduce Steps to reproduce the behavior: Just disconnect with one of the latest version of smack or any other client
Impact Smack waits for end of streams from the server and wait until a timeout expires
Expected behavior The server should sends the end of the stream so the client know that all packets has been processed correctly
Details (please complete the following information):
The text was updated successfully, but these errors were encountered:
Thank you for reporting it. We will fix it in one of the upcoming minor versions.
(ref: #server-1299)
Sorry, something went wrong.
Any update with this? It has been fixed in a new minor?
It hasn't been addressed yet.
No branches or pull requests
Describe the bug
A problem has emerged while upgrading to a new version of smack, it seems that the client sends the end of stream </stream:stream> but the server did not sends it back
Full discussion with network traffic here:
https://discourse.igniterealtime.org/t/smack-timeout-during-disconnect/90651/5
To Reproduce
Steps to reproduce the behavior:
Just disconnect with one of the latest version of smack or any other client
Impact
Smack waits for end of streams from the server and wait until a timeout expires
Expected behavior
The server should sends the end of the stream so the client know that all packets has been processed correctly
Details (please complete the following information):
The text was updated successfully, but these errors were encountered: