Websocket stops receiving data with no status change
See original GitHub issue- Connect to websocket v2 with a paid account (polygon: true).
- Subscribes to trades (on any ticker)
- Data streams properly for < 2 hours, then abruptly goes silent without any apparent status change.
[edit] When connecting to Alpaca stream directly from cli using $ wscat
the websocket works as expected. I just streamed trades up from around 1pm to 7.20pm (EST) today.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
WebSocket server stops sending data to client after a time
While we are getting prices from the server normally, after a time, it stops to send both the prices and PING message to...
Read more >Websocket stops receiving messages · Issue #11 - GitHub
Usually when messages stop coming through it means the data isn't being consumed fast enough. There is a server side buffer and if...
Read more >Handling connection loss with websockets - Stack Overflow
My TypeScript implementation in an Angular app to handle WebSocket Connection lost. This does not use PING PONG strategy in order to avoid...
Read more >Troubleshooting connection issues | Socket.IO
You are trying to reach a plain WebSocket server; The server is not reachable; The client is not compatible with the version of...
Read more >ws - npm
ws is a simple to use, blazing fast, and thoroughly tested WebSocket client and server implementation. Passes the quite extensive Autobahn test ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hello, we will investigate this!
In the latest release the SDK was extended with reconnection after not getting any ping from the server. I hope this could prevent from the situations like yours. I close this ticket, if you have something more please open a new one.