pusher-http-ruby: Pusher::HTTPError: execution expired (HTTPClient::ConnectTimeoutError)
Having problem with Pusher Pusher::HTTPError: execution expired (HTTPClient::ConnectTimeoutError)
i also increased the timeout, yet no change. this happens in Rails 4.2.4 console, controller and Delayed::Job
what could be wrong?
2.2.2 :009 > Pusher.timeout=360000
=> 360000
2.2.2 :010 > Pusher.trigger(‘test_channel’, ‘my_event’, {message: ‘hello world’})
Pusher::HTTPError: execution expired (HTTPClient::ConnectTimeoutError)
from /home/vg/.rvm/gems/ruby-2.2.2/gems/pusher-0.14.5/lib/pusher/request.rb:33:in rescue in send_sync' from /home/vg/.rvm/gems/ruby-2.2.2/gems/pusher-0.14.5/lib/pusher/request.rb:27:insend_sync’
from /home/vg/.rvm/gems/ruby-2.2.2/gems/pusher-0.14.5/lib/pusher/resource.rb:18:in post' from /home/vg/.rvm/gems/ruby-2.2.2/gems/pusher-0.14.5/lib/pusher/client.rb:144:inpost’
from /home/vg/.rvm/gems/ruby-2.2.2/gems/pusher-0.14.5/lib/pusher/client.rb:228:in trigger' from (irb):10 from /home/vg/.rvm/gems/ruby-2.2.2/gems/railties-4.2.4/lib/rails/commands/console.rb:110:instart’
from /home/vg/.rvm/gems/ruby-2.2.2/gems/railties-4.2.4/lib/rails/commands/console.rb:9:in start' from /home/vg/.rvm/gems/ruby-2.2.2/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:68:inconsole’
from /home/vg/.rvm/gems/ruby-2.2.2/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:39:in run_command!' from /home/vg/.rvm/gems/ruby-2.2.2/gems/railties-4.2.4/lib/rails/commands.rb:17:in<top (required)>’
from /home/vg/.rvm/gems/ruby-2.2.2/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:274:in require' from /home/vg/.rvm/gems/ruby-2.2.2/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:274:inblock in require’
from /home/vg/.rvm/gems/ruby-2.2.2/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:240:in load_dependency' from /home/vg/.rvm/gems/ruby-2.2.2/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:274:inrequire’
from /home/vg/tongs/last/uae/foodiac-ae-api/bin/rails:8:in <top (required)>' from /home/vg/.rvm/gems/ruby-2.2.2/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:268:inload’
from /home/loista/.rvm/gems/ruby-2.2.2/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:268:in block in load' from /home/loista/.rvm/gems/ruby-2.2.2/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:240:inload_dependency’
from /home/vg/.rvm/gems/ruby-2.2.2/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:268:in load' from /home/vg/.rvm/rubies/ruby-2.2.2/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:inrequire’
from /home/vg/.rvm/rubies/ruby-2.2.2/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in require' from -e:1:in<main>'2.2.2 :011 >
2.2.2 :012 >
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 41 (9 by maintainers)
I appreciate this is a frustrating issue; but if I could please ask people to refrain from +1 that’d be great. We’re struggling to recreate this problem; if you’re seeing it any info on your stack, when it happens, any logging, info, etc that you can say is way more productive and useful than a ‘+1’. Thanks 😃
I emailed their support and they basically said “deal with it.”
I asked
To which he agreed
So that’s what we’re implementing now.
Update: Exponential backoff is working fine.
@qlimaxx thanks for that info, you inspired me. It looks like these config methods are also exposed, maybe worth experimenting with:
For now I will set
Pusher.timeout = 30As I understood the problem is that the default timeout is 5s in Pusher. You can switch it to a higher value like 30s. I tested with Pusher 1.3.1
Pusher.timeout = 30@bitboxer @Juanchote We’re investigating the cause of timeouts for the Push Notifications API. This would be the cause for it occurring as frequently as you claim it does.
You can follow along progress here : https://status.pusher.com.
Thanks for your patience!