Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Possible connection leak? A new SSE connection is opened on every onerror status=undefined
See original GitHub issueHi @Yaffle need your help in figuring this out. I see a pattern where a new connection is opened on every onerror and the status for the on error is status=undefined. The client does not get any data through SSE connection and after few seconds onerror with status=undefined is invoked again and a new connection is made to the backend.
All these connections kept open till the browser/session is closed and all the connections are closed together.
Could you please help in figuring this out and understand why this is happening and help in fixing it?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@Yaffle I can, thanks. Sadly, my error was due to a bug in our production deployment where my keep-alives weren’t getting through in specific instances. Fixing those has alleviated the triggering of this error message in most cases.
I will try it and cause the error a few times and report back.
@Yaffle Sorry it’s taken me a bit. I see an error message explaining the issue and a call stack. Seems good to me.
Since you say ‘Reconnecting’ I’m guessing I don’t need to re-open the connection manually (which I’m currently doing).
We send a keep-alive every 25 seconds…so I’ll have to look into why that isn’t being found by the polyfilll as I can confirm it’s sent. That seems to be an entirely separate issue from this, though.