You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After establishing a WebSocket notification connection between the Cryostat server and web-client UI the connection is left idle, unless some activity happens and triggers the emission of a notification event.
If the connection is idle for long enough it will be closed (by the browser?):
The web-client knows to retry opening a WebSocket connection when it is disconnected, so the connection is re-established almost immediately.
Expected Behavior
WebSocket ping frames should be sent periodically so that the connection is kept alive and the web-client application code does not need to attempt to reconnect.
Current Behavior
After establishing a WebSocket notification connection between the Cryostat server and web-client UI the connection is left idle, unless some activity happens and triggers the emission of a notification event.
If the connection is idle for long enough it will be closed (by the browser?):
The web-client knows to retry opening a WebSocket connection when it is disconnected, so the connection is re-established almost immediately.
Expected Behavior
WebSocket ping frames should be sent periodically so that the connection is kept alive and the web-client application code does not need to attempt to reconnect.
Older Cryostat versions did this every 5 seconds: https://github.com/cryostatio/cryostat/blob/ed1fcbd31d8e2d759b85397a29414959c9e40df9/src/main/java/io/cryostat/messaging/MessagingServer.java#L184 . This is probably much faster than it needs to be: https://stackoverflow.com/questions/14576298/how-to-decide-the-ping-interval-for-websocket-connection
Steps To Reproduce
No response
Environment
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: