Intermittent problems using with celluloid about pusher-http-ruby HOT 5 CLOSED

Hi,

I'm not really familiar with celluloid and if it works well with httpclient (the underlying HTTP lib we're using). If it's using multiple threads there might be some concurrency issue in regards to keep-alive. I recommend using 1 pusher instance per thread to see if it fixes the issue. Concurrent access to $outstanding_requests might also be an issue but that shouldn't affect the pusher gem.

The timeout is the default one in the library, see 7dca547 . Any link between your server and ours might fail so adding a retry is definitely a good idea.

from pusher-http-ruby.

It might be easier to create 8 threads and then publish to a Queue object like that: https://gist.github.com/zimbatm/334b4337e61a43e12908

from pusher-http-ruby.

@zimbatm I'm experiencing thread-safety problems as well. Try to not reuse the same Pusher::Client instance, but create a new one before to use it. https://gist.github.com/zimbatm/334b4337e61a43e12908#file-test-rb-L19

It will be probably slower, but better safe than sorry.

from pusher-http-ruby.

Unless Celluloid is changing ruby radically it should be safe enough to have 1 ruby client per thread. Creating a new instance for each request means not being able to use HTTP keep-alive.

from pusher-http-ruby.

Closing for lack of reproducibility. I believe Celluloid is also now deprecated. For example sidekiq has switched to use the concurrent-ruby gem.

from pusher-http-ruby.