-
In NestJS GraphQL Subscription (graphql-ws), The error is occurring for an unknown reason. "RangeError: Invalid Websocket frame: invalid payload length 126" When this error appears, it shuts down the server, which is very fatal. I think, problem point is graphql-ws or nestjs8 (graphql) minimum reproduction link : https://github.com/maemenaver/nestjs-graphql-ws-issue |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 14 replies
-
From websockets/ws#1662 (comment):
You most probably have an error thrown during the execution whose message is trying to be sent to the client, but it fails because the error message is too big. I guess here: Lines 107 to 117 in c47dcf0 |
Beta Was this translation helpful? Give feedback.
-
An error occurred during the massage handling phase and its message is too long. Luckily, with |
Beta Was this translation helpful? Give feedback.
-
Still getting this error when using gracefull restart RangeError: Invalid WebSocket frame: invalid payload length 126 |
Beta Was this translation helpful? Give feedback.
-
Additionally, with |
Beta Was this translation helpful? Give feedback.
Additionally, with
v5.5.4
, all emitted errors events (both on the WebSocket server and each distinct socket) will have the transmitted messages limited and errors will be logged to the console. Please update thegraphql-ws
version.