fix(transport): align WebSocket read limits with agent protocol
This commit is contained in:
1 parent
ef6e65e6f1
commit
6984a09486
11 files changed
+376
-4
No files matched your search
@@ -126,6 +126,16 @@ exact ignored `dist/` directory after preserving any evidence.
|
||||
|
||||
## Common incidents
|
||||
|
||||
- **Reconnect loop after a command produces substantial output:** inspect
|
||||
`C:\ProgramData\RVBox\service-startup.log` on Windows and the server log for
|
||||
`StatusMessageTooBig` / `read limited at 32769 bytes`. Early v1 transports
|
||||
inherited a 32 KiB WebSocket ceiling despite permitting 64 KiB chunks and
|
||||
1 MiB envelopes. Both transports now set the configured envelope ceiling
|
||||
before reading any messages. Upgrade the server first to drain pending
|
||||
client output, then the client for large dispatch/reconciliation responses.
|
||||
Preserve spool/history: rebooting cannot remove a replayable oversized event.
|
||||
New server logs include bounded read/reconciliation errors and an
|
||||
`agent_message_too_big` counter; new clients advertise the actual build version.
|
||||
- **No client / stale session:** verify nginx has WebSocket `101` entries for
|
||||
`/v1/agent`, server readiness is true, and the Windows service is running.
|
||||
Use `rvc stat CLIENT_ID`; do not restart the client merely to clear history.
|
||||
|
||||
Reference in new issue
Block a user