WebSocket keep-alive is not working as expected
Description
Environment
is related to
relates to
Activity
Dele Olajide May 18, 2020 at 12:28 PM
Websockets keep-alive was broken by the stream management implementation. Websockets is missing stream resumption implementation and this was causing the issue. This issue is resolved by stopping Openfire from advertising stream resumption for websockets.
This issue will be followed up with a new issue that implements stream resumption for websockets.
Dele Olajide May 6, 2020 at 1:35 PM
The root of this issue is this
The ability to resume XEP-0198 streams for websockets has not yet been implemented. This causes the xmpp session to always remain open when the websocket closes. The solution for now is to remove the check and always close the xmpp session when the websocket closes.
wroot April 27, 2020 at 6:41 PM
There are some professional (paid) services available http://www.igniterealtime.org/support/service_providers.jsp
Eryn Benson April 27, 2020 at 11:47 AM
If there is anything we can do to see this issue fixed please let us know! We are very keen to see a resolution so we can use websockets. Thanks team.
Sundeep Vig March 10, 2020 at 7:24 PMEdited
This is still happening in OF 4.5.1. Websocket sessions are living forever - till server restart. Killing them from the admin console does not seem to help either. This is making websockets unusable. Have not tried with disabled stream management. Explicit logout is removing the session from the server.
Could this be prioritized for a fix please?
WebSocket plugin has a keep-alive mechanism that is designed to detect broken connections and close the corresponding sessions. However, it appears this is not working as expected.