Rainbows on Heroku Issues

Rainbows on Heroku Issues

[Kunal Modi]

Hi,

I am trying to run Rainbows on Heroku and I'm getting some odd errors,
I was wondering if anyone had any explanation / idea on how to solve.
I created a simple Rails 3.1/Ruby 1.9.3 app to test Unicorn/Rainbows
on Heroku (just a simple endpoint that responds with simple json). The
app worked as expected with Unicorn, but has some odd tendencies on
Heroku when using Rainbows.

The request completely processes in Heroku, but always waits
keepalive_timeout time before actually returning the response:
2012-06-06T22:33:01+00:00 app[web.1]: Started GET "/" at 2012-06-06
22:33:01 +0000
2012-06-06T22:33:01+00:00 app[web.1]: cache: [GET /] miss
2012-06-06T22:33:06+00:00 heroku[router]: GET
simple-waterfall-3300.herokuapp.com/ dyno=web.1 queue=0 wait=0ms
service=5020ms status=200 bytes=13

When I changed keepalive timeout to 10s, the responses were similarly
delayed by 10s. When I set the keelalive timeout to 0, Heroku returned
2012-06-07T00:50:02+00:00 heroku[router]: Error H13 (Connection closed
without response)


My Rainbows specific config was:
  use :ThreadPool
  worker_connections 30
  keepalive_timeout 5



Thanks a lot!
Kunal
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying

Re: Rainbows on Heroku Issues

[Eric Wong]

Kunal Modi <kunalm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> I am trying to run Rainbows on Heroku and I'm getting some odd errors,
> I was wondering if anyone had any explanation / idea on how to solve.
> I created a simple Rails 3.1/Ruby 1.9.3 app to test Unicorn/Rainbows
> on Heroku (just a simple endpoint that responds with simple json). The
> app worked as expected with Unicorn, but has some odd tendencies on
> Heroku when using Rainbows.
> 
> The request completely processes in Heroku, but always waits
> keepalive_timeout time before actually returning the response:

Try adding Rack::ContentLength and/or Rack::Chunked middleware.

You might be missing a Content-Length or "Transfer-Encoding: chunked"
header in the response, so the client is assuming HTTP/1.0 semantics
and waiting for the connection to close.  HTTP/1.1 requires either
Content-Length or chunked transfer-encoding to do persistent
connections.
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying