Websockets transport stuck during the close step of a connection
See original GitHub issueI am using the gql from master and experiencing an occasional deadlock. The library I’m using is calling client.execute()
with a websocket transport. Sometimes I see an error like this: Exception in subscribe: GeneratorExit()
and then client.execute()
never returns.
WebSocketTransport.execute()
does return an ExecutionResult
, i.e. first_result
is set. Also AsyncClientSession.execute()
returns.
Maybe it’s failing to close the connection?
Issue Analytics
- State:
- Created 3 years ago
- Comments:15
Top Results From Across the Web
websocket closing connection automatically - Stack Overflow
I'm building an application in java that has an embedded websocket server based on jetty. The client is the default websocket implementation in...
Read more >Troubleshooting connection issues | Socket.IO
the socket is not able to connect; the socket gets disconnected; the socket is stuck in HTTP long-polling; other common gotchas ...
Read more >Having trouble calling a websocket using Aspnetcore Signalr ...
User1031775717 posted. Hi,. I'm trying to call a websocket service located at wss://socket.btcmarkets.net/v2 using Aspnetcore Signalr Client ...
Read more >dedicated agents are not able to connect
Since CloudBees Core 2.222.1.1 it is possible to connect your inbound agents using WebSocket transport instead of TCP, which simplifies the connectivity at...
Read more >WebSockets and Node.js - testing WS and SockJS by building ...
WebSockets on the server can become complicated as the connection upgrade from HTTP to WebSockets requires handling. This is why developers commonly use...
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 FreeTop 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
Top GitHub Comments
I have been testing your new code for 30 minutes or so. Seems to be working 😃
This is now fixed in version 3.0.0a2