search

strongloop / strong-cluster-socket.io-store

Implementation of socket.io store using node's native cluster messaging
Other
23 stars 3 forks source link

AssertionError: Invalid topic "disconnect:3jjhnPfKZVtle28NqGCa". #8

Closed abdula closed 11 years ago

abdula commented 11 years ago

AssertionError: Invalid topic "disconnect:3jjhnPfKZVtle28NqGCa". Topic patterns must be .-separated alphanumeric words at check (/home/abdula/projects/node/acro-office-v2/src/acro-office/node_modules/strong-mq/lib/topic.js:34:5) at NativePublishQueue.workerPublish as publish at ClusterStore.publish (/home/abdula/projects/node/acro-office-v2/src/acro-office/node_modules/strong-cluster-socket.io-store/lib/cluster-store.js:62:15) at XHRPolling.Transport.end (/home/abdula/projects/node/acro-office-v2/src/acro-office/node_modules/socket.io/lib/transport.js:469:18)

sam-github commented 11 years ago

Can you confirm this fixes the problem you are seeing?

https://github.com/strongloop/strong-cluster-socket.io-store/commit/984fd7df1a96b3beb0da43bfa2cf1b9ccb910148 should fix this.

We haven't released this to npmjs.org yet, but will soon.

abdula commented 11 years ago

After 984fd7d in log of socket.io: warn - client not handshaken client should reconnect warn - client not handshaken client should reconnect warn - client not handshaken client should reconnect

bajtos commented 11 years ago

After 984fd7d in log of socket.io: warn - client not handshaken client should reconnect warn - client not handshaken client should reconnect warn - client not handshaken client should reconnect

This is a know bug of socket.io, a fix would require significant redesign of socket.io internals. See LearnBoost/socket.io#952. I am afraid this issue is not going to get fixed anytime soon.

I'd recommend you setup a load-balancer that supports session affinity (sticky sessions), e.g. HAProxy.