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
Wait for the first RETRY.
=> GraphQlTransportException => connection refused.
Run the server.
KO -> the next retry will fail with the same reason.
Case 2:
Run the server.
Run the client.
Shutdown the server.
FIRST RETRY
=> WebSocketDisconnectedException -> connection is closed or lost.
Wait for the SECOND RETRY.
=> GraphQlTransportException => connection refused.
Run the server.
KO -> the next retry will fail with the same reason.
Working Case:
Run the server.
Run the client.
Shutdown the server.
Wait for the FIRST RETRY.
=> WebSocketDisconnectedException -> connection is closed or lost.
Run the server.
OK, the retry is working.
Is there a way to resume a WebSocket connection when the client failed to connect to the remote server?
The text was updated successfully, but these errors were encountered:
jma-9code
changed the title
Unable to retry WebSocketGraphQlClient if he can't connect to the server one time
WebSocketGraphQlClient Unable to Retry Connection after Initial Connection Failure
Sep 22, 2023
I confirm there is an issue. For the version, I think you mean Boot 3.1.4 as 3.2 is not GA yet.
rstoyanchev
changed the title
WebSocketGraphQlClient Unable to Retry Connection after Initial Connection Failure
WebSocketGraphQlClient unable to connect after the first reconnect failure
Oct 27, 2023
rstoyanchev
changed the title
WebSocketGraphQlClient unable to connect after the first reconnect failure
WebSocketGraphQlClient unable to reconnect after the first reconnect failure
Oct 27, 2023
Context:
Using Spring Boot 3.2.4 with Spring WebFlux/GraphQL.
Server A exposes a graphqlSubscription, and Server B consumes the subscription. They both use the same components (reactor/netty).
Steps to Reproduce:
Client Sample:
Not Working Cases:
Case 1:
=> GraphQlTransportException => connection refused.
Case 2:
=> WebSocketDisconnectedException -> connection is closed or lost.
=> GraphQlTransportException => connection refused.
Working Case:
=> WebSocketDisconnectedException -> connection is closed or lost.
Is there a way to resume a WebSocket connection when the client failed to connect to the remote server?
The text was updated successfully, but these errors were encountered: