|Weird error on socket.io garbage collector||Sergio Canales||1/7/13 2:24 PM|
Has anyone encountered this error:
TypeError: Cannot use 'in' operator to search for 'issued' in null
at String.IN (native)
at Manager.garbageCollection (/node_modules/socket.io/lib/manager.js:1021:21)
at Timer. (native)
at Timer.ontimeout (timers.js:223:14)
It seems to be something related to the handshake that is cleaned up on the GarbageCollector method on manager.js file.
Here is a link to the pull request for this GC method (https://github.com/LearnBoost/socket.io/pull/408), can anyone tell me anything about this?
I've done a temporary fix by checking for null on that if condition, but something tells me there's something wrong going on somewhere else.
|Re: Weird error on socket.io garbage collector||Lassi Kinnunen||2/14/13 3:43 AM|
earlier in the autumn it at least proved very tricky for us to get the built in redis clustering to work reliably so that the socket.io instances would stay in sync(it would leak rooms, sometimes).
our fix was to use redis-pub sub instead of rooms, while waiting for proper cluster support for socket.io. redis pubsub is fairly simple and ended up being almost as much/little code as doing it via the socket.io provided redis support and this has provided us with crash/leak free environment running for several months.
On Monday, January 28, 2013 10:11:48 PM UTC+2, la...@iamat.com wrote: