Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there really no way to guarantee correct connection count? #129

Open
FOMNick opened this issue May 16, 2012 · 1 comment
Open

Is there really no way to guarantee correct connection count? #129

FOMNick opened this issue May 16, 2012 · 1 comment

Comments

@FOMNick
Copy link

FOMNick commented May 16, 2012

I followed the connection roster example and it seems to work great aside from a a quirk:
Over time, I found that my session counts were getting out of whack. Forcing a restart on the juggernaut process while my Rails server is running produces a subscribe event, but never an unsubscribe event in the event that the juggernaut server goes down. The session count is completely unchecked by a corresponding unsubscribe event in this scenario. Is there any way to combat this issue?

@comboy
Copy link

comboy commented Jun 30, 2012

#77

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants