Rails 4, Live Streaming, stays open, blocking requests

Question

I'm trying to use Rails 4 Live Streaming component. It all works except that it seems like the stream stays open and blocks new request.

How can I ensure that the connection close down properly when closing down or clicking on a new link within the application?

This is my live event controller.

  def events
    response.headers["Content-Type"] = "text/event-stream"
    redis = Redis.new
    redis.psubscribe("participants.*") do |on|
      on.pmessage do |pattern, event, data|
        response.stream.write("event: #{event}\n")
        response.stream.write("data: #{data}\n\n")
      end
    end
  rescue IOError
  ensure
    redis.quit
    response.stream.close
  end

Database conf

production:
  adapter: postgresql
  encoding: unicode
  database: ************
  pool: 1000
  username: ************
  password: ************
  timeout: 5000

I'm using puma as standalone webserver (i don't have heavy static files that need to be served by nginx) on Ubuntu 10.04 with postgresql 9.2.x.

Were you ever able to solve this problem? Dan's answer is a good summary of what's going on but doesn't quite answer the question (I assume for you as well since you didn't accept it). — Paul Richter, Sep 23 '13 at 22:52
@Teeg As you wrote, it's a good summary but it didn't solve my question. I ended up using Faye instead, which is sad because I really wanted this to work properly. — Philip, Sep 24 '13 at 09:20
Thats too bad. I've posted a [similar question](http://stackoverflow.com/q/18970458/877472) that contains a goofy solution. I'll let you know if I ever figure it out. — Paul Richter, Sep 24 '13 at 17:40

score 8 · Answer 1 · answered Sep 06 '13 at 16:22

8

You have to change the development environment settings to enable this feature.

Add or change this in your config/environments/development.rb:

config.cache_classes = true
config.eager_load = true

See http://railscasts.com/episodes/401-actioncontroller-live?view=asciicast

answered Sep 06 '13 at 16:22

Michael Schäfermeyer

2,794
1
16
8

This actually solves the problem in my case. Many thanks. – Nafaa Boutefer Nov 02 '15 at 07:23

Dan · Answer 2 · 2013-08-26T23:45:15.600

Puma shouldn't be blocking and should allow multiple threads to allow multiple requests.

To walk you through what is happening in your code. You are currently using two threads in this code per request. The thread the request came in on, and a background thread used to hold open the connection.

Your connections will properly close due to the ensure block at the end of your action method.

def events
  response.headers["Content-Type"] = "text/event-stream"
  redis = Redis.new
  # blocks the current thread
  redis.psubscribe("participants.*") do |on|
    on.pmessage do |pattern, event, data|
      response.stream.write("event: #{event}\n")
      response.stream.write("data: #{data}\n\n")
    end
  end
  # stream is on a background thread and will remain open until
  # redis.psubscrie exits. (IO Error, etc)
rescue IOError
ensure
  redis.quit
  response.stream.close
end

You could also investigate another server called rainbows (http://rainbows.rubyforge.org/index.html) which is another very good rack server for open requests.

Here is also a thread related to streaming threads hanging https://github.com/rails/rails/issues/10989

Rails 4, Live Streaming, stays open, blocking requests

2 Answers2

Linked