parse-community / parse-community/parse-server
[LiveQuery]RangeError: Invalid WebSocket frame: invalid payload length 126
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
Related to #6173
Issue Description
RangeError: Invalid WebSocket frame: invalid payload length 126
This error occurs intermittently and stops the server when I use livequery.
Steps to reproduce
- Run livequery by Parse Server
- Use livequery
- It happens irregularly
Expected Results
Parse Server should not terminate by the error.
Actual Outcome
Parse Server is terminated.
RangeError: Invalid WebSocket frame: invalid payload length 126
at Receiver.getInfo (/var/app/current/node_modules/parse-server/node_modules/ws/lib/receiver.js:213:16)
at Receiver.startLoop (/var/app/current/node_modules/parse-server/node_modules/ws/lib/receiver.js:127:22)
at Receiver._write (/var/app/current/node_modules/parse-server/node_modules/ws/lib/receiver.js:74:10)
at doWrite (_stream_writable.js:435:12)
at writeOrBuffer (_stream_writable.js:419:5)
at Receiver.Writable.write (_stream_writable.js:309:11)
at Socket.socketOnData (/var/app/current/node_modules/parse-server/node_modules/ws/lib/websocket.js:875:35)
at Socket.emit (events.js:223:5)
at Socket.EventEmitter.emit (domain.js:475:20)
at addChunk (_stream_readable.js:309:12)
/var/app/current/node_modules/parse-server/lib/ParseServer.js:229
throw err;
^
RangeError: Invalid WebSocket frame: invalid payload length 126
at Receiver.getInfo (/var/app/current/node_modules/parse-server/node_modules/ws/lib/receiver.js:213:16)
at Receiver.startLoop (/var/app/current/node_modules/parse-server/node_modules/ws/lib/receiver.js:127:22)
at Receiver._write (/var/app/current/node_modules/parse-server/node_modules/ws/lib/receiver.js:74:10)
at doWrite (_stream_writable.js:435:12)
at writeOrBuffer (_stream_writable.js:419:5)
at Receiver.Writable.write (_stream_writable.js:309:11)
at Socket.socketOnData (/var/app/current/node_modules/parse-server/node_modules/ws/lib/websocket.js:875:35)
at Socket.emit (events.js:223:5)
at Socket.EventEmitter.emit (domain.js:475:20)
at addChunk (_stream_readable.js:309:12)
Emitted 'error' event on WebSocket instance at:
at Receiver.receiverOnError (/var/app/current/node_modules/parse-server/node_modules/ws/lib/websocket.js:780:13)
at Receiver.emit (events.js:223:5)
at Receiver.EventEmitter.emit (domain.js:475:20)
at errorOrDestroy (internal/streams/destroy.js:108:12)
at onwriteError (_stream_writable.js:450:5)
at onwrite (_stream_writable.js:477:5)
at Receiver.startLoop (/var/app/current/node_modules/parse-server/node_modules/ws/lib/receiver.js:148:5)
at Receiver._write (/var/app/current/node_modules/parse-server/node_modules/ws/lib/receiver.js:74:10)
at doWrite (_stream_writable.js:435:12)
at writeOrBuffer (_stream_writable.js:419:5) {
[Symbol(status-code)]: 1002
}
Environment Setup
-
Server
- NodeJS version: [12.14.1]
- parse-server version (Be specific! Don't say 'latest'.) : [3.10.0]
- Operating System: [Mac and Linux]
- Hardware: []
- Localhost or remote server?: [Local and AWS]
-
Database
- PostgreSQL version: [11.4 ~ 11.5]
- Storage engine: [RDS]
- Hardware: []
- Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): [Local and AWS]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the LiveQuery setup and the error path shown in lib/ParseServer.js:229, then inspect the reported ws Receiver stack. Try to reproduce the intermittent failure while using LiveQuery with the listed Node.js and Parse Server versions. Done means the server no longer terminates when this invalid WebSocket frame error occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100