SocketCluster / SocketCluster/socketcluster
Socket hung up in scc-broker
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
my state serevr is already running
i run
set SCC_STATE_SERVER_HOST=127.0.0.1 && set SCC_BROKER_SERVER_PORT=3300 && node server.js
and i get the error
{ SocketProtocolError: Socket hung up
at SCClientSocket._onSCClose (D:\arash\socketCluster\scc-broker\node_modules\socketcluster-client\lib\scclientsocket.js:647:15)
at SCTransport.<anonymous> (D:\arash\socketCluster\scc-broker\node_modules\socketcluster-client\lib\scclientsocket.js:297:12)
at SCTransport.Emitter.emit (D:\arash\socketCluster\scc-broker\node_modules\component-emitter\index.js:133:20)
at SCTransport._onClose (D:\arash\socketCluster\scc-broker\node_modules\socketcluster-client\lib\sctransport.js:217:28)
at WebSocket.SCTransport.wsSocket.onerror (D:\arash\socketCluster\scc-broker\node_modules\socketcluster-client\lib\sctransport.js:81:12)
at WebSocket.onError (D:\arash\socketCluster\scc-broker\node_modules\ws\lib\event-target.js:128:16)
at emitOne (events.js:116:13)
at WebSocket.emit (events.js:211:7)
at ClientRequest.req.on (D:\arash\socketCluster\scc-broker\node_modules\ws\lib\websocket.js:535:10)
at emitOne (events.js:116:13)
name: 'SocketProtocolError',
message: 'Socket hung up',
Contributor guide
No contributing guide indexed for this repository
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 by reproducing the command from server.js with SCC_STATE_SERVER_HOST=127.0.0.1 and SCC_BROKER_SERVER_PORT=3300, then trace the disconnect through the reported socketcluster-client and ws files. Done means identifying why the broker connection closes and documenting or correcting the cause with a verified rerun.
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
- 18/100