Kert Heinecke

I solve this by not testing in irb. Had it running in production now for two months and it works great. why persistence doesn't work in irb I never tested....

First and foremost, what if any error message do you get? Where are your setting it to persist? What does your over all worker config look like? When is this...

I have a separate worker class just for push. I open a persistent connection for the class and leave it open. This should be done along with your other configs...

Related bug, gem does not handle a single regex properly. Forces you to pass it in as an array which results in the same browser error mentioned in this thread.

Ahh, likely the issue. I pulled it from ruby gems. The issue seemed to be that it took the single regex, but if it passed, it was assigning the regex...