socketcluster: Got errors when run in ssl mode

Got errors when run in ssl mode, however, when run in non ssl mode it works fine:

1474625965853 - Origin: Worker (PID 40324)
   [Error] TypeError: SCSocket.prototype.stringify is not a function
    at EventEmitter.Client._handleExchangeMessage (/Users/hustcer/github/lark/node_modules/sc-broker-cluster/index.js:645:54)
    at emitTwo (events.js:106:13)
    at EventEmitter.emit (events.js:191:7)
    at EventEmitter.emit (/Users/hustcer/github/lark/node_modules/sc-domain/index.js:12:31)
    at EventEmitter.handleMessage (/Users/hustcer/github/lark/node_modules/sc-broker-cluster/clientcluster.js:10:15)
    at emitTwo (events.js:111:20)
    at EventEmitter.emit (events.js:191:7)
    at EventEmitter.emit (/Users/hustcer/github/lark/node_modules/sc-domain/index.js:12:31)
    at Socket.<anonymous> (/Users/hustcer/github/lark/node_modules/sc-broker/index.js:233:12)
    at emitOne (events.js:96:13)
1474625965860 - Worker 0 exited - Exit code: 1

And the error causing worker to crash/respawn.

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 18 (16 by maintainers)

Most upvoted comments

Two atoms are talking and one atom says, “Hey man, I think I lost an electron”. The other atom says, “Are you positive?”…

happilymarrieddad on Sep 23, 2016

I just have to be more careful. Maybe I should wait till the weekend to publish risky changes. Even well established projects will occasionally release a buggy version.

I really should write more tests and think of adding CI to prevent these kinds of issues.

jondubois on Sep 23, 2016

@jondubois hey man I think we can close this one.

happilymarrieddad on Oct 19, 2016