Details
-
Type:
Story
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Won't Do
-
Component/s: sse-gateway-plugin
-
Labels:None
-
Similar Issues:
-
Epic Link:
-
Sprint:1.0-m11, 1.0-m12
Description
Doing this should get rid of a scary (but harmless) looking browser console errors when the SSE connection is unexpectedly dropped e.g. by an intermediary proxy/gateway.
By doing this periodically from the client side (disconnecting and reconnecting), we avoid the user seeing this.
The error looks scary but is actually fine because the SSE EventSource auto-reconnects.
Something to consider though .... we might need to do some sort of "store and forward" at the gateway for when messages arrive during a reconnect. See JENKINS-36238
Attachments
Issue Links
- is duplicated by
-
JENKINS-35764 Make SSE Gateway connection keep-alive configurable
-
- Closed
-
- is related to
-
JENKINS-36054 Reload page after hibernate
-
- Closed
-
-
JENKINS-36238 Server-side store and forward SSE events during a reconnect
-
- Resolved
-
Not really needed now because we have the connection timeout set so low that this should no longer be an issue. Those scary browser console errors (as seen on dogfood) should be a thing of the past now too.