WebSocket 1009 Message Too Big vs 1012 Service Restart
Both WebSocket 1009 (Message Too Big) and 1012 (Service Restart) belong to the WebSocket Close Codes category. 1009 indicates that an endpoint is terminating the connection because it received a message that is too large for it to process. Meanwhile, 1012 means that the server is terminating the connection because it is restarting. The client should reconnect after a brief delay.
説明
An endpoint is terminating the connection because it received a message that is too large for it to process.
このコードが表示される場合
The message payload exceeded the server's configured maximum frame or message size limit. Common when uploading large files or sending huge JSON payloads over WebSocket.
解決方法
Reduce the message size by chunking large payloads into smaller frames. Alternatively, increase the server's max message size configuration if the large payload is expected.
説明
The server is terminating the connection because it is restarting. The client should reconnect after a brief delay.
このコードが表示される場合
The server is performing a planned restart — for example, during a deployment or configuration reload. The connection will be available again shortly.
解決方法
Implement automatic reconnection with a short delay (1-5 seconds). This code signals that reconnecting is expected and should succeed once the server is back up.
主な違い
WebSocket 1009: An endpoint is terminating the connection because it received a message that is too large for it to process.
WebSocket 1012: The server is terminating the connection because it is restarting. The client should reconnect after a brief delay.
You encounter 1009 when the message payload exceeded the server's configured maximum frame or message size limit. Common when uploading large files or sending huge JSON payloads over WebSocket.
You encounter 1012 when the server is performing a planned restart — for example, during a deployment or configuration reload. The connection will be available again shortly.
どちらをいつ使うか
For 1009 (Message Too Big): Reduce the message size by chunking large payloads into smaller frames. Alternatively, increase the server's max message size configuration if the large payload is expected. For 1012 (Service Restart): Implement automatic reconnection with a short delay (1-5 seconds). This code signals that reconnecting is expected and should succeed once the server is back up.