Persisted connections are not re-connecting in case they are dropped about houston

[joefiorini]

Potentially related to #77?

[micred]

Almost an year ago a guy has resolved by himself: http://joshsymonds.com/blog/2013/10/17/sidekiq-plus-houston-production-ready/
Maybe is maintainer consider the code safe, it will be cool to have the begin-rescue-5attemps code imported in the gem.

[sorted-bits]

@micred I am using your solution, but I still have the problem when a token is invalid, it completely stops sending push notifications. The connection.open? method still returns true, but this does not seem to be correct.

[micred]

yeah, I know :-(
To fix that problem (as a temporary workaround) I have added a "sleep 0.2" between each message sent.

[sorted-bits]

That does not solve my problem. I already filter out old tokens but sometimes there is a token in my database that isn't valid and every notification after that token is not receiving a push message. :(

[ferrous]

A lazy wrap with reset on CLOSE_WAIT connections (working on linux)
https://gist.github.com/ferrous/d498971be300683c3bbd