We're updating the issue view to help you get more done. 

WebSocket keep-alive is not working as expected

Description

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.

Environment

None

Acceptance Test - Entry

None

Activity

Show:
Sundeep Vig
March 10, 2020, 7:24 PM
Edited

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?

Eryn Benson
April 27, 2020, 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.

wroot
April 27, 2020, 6:41 PM

There are some professional (paid) services available http://www.igniterealtime.org/support/service_providers.jsp

Dele Olajide
May 6, 2020, 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.

 

 

Dele Olajide
May 18, 2020, 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.

Fixed

Assignee

Dele Olajide

Reporter

Tom Evans

Labels

None

Expected Effort

None

Ignite Forum URL

None

Fix versions

Affects versions

Priority

Major
Configure