Geek asks and answers

Error H13 (connection closed without response) Heroku

I am working on Ruby on Rails. A project that works fine on the local server, and when I deploy it to a hero, it gives the following error. Thank!

2012-06-12T14:19:23+00:00 heroku[router]: Error H13 (Connection closed without response) -> GET sheets-vip.heroku.com/ dyno=web.1 queue= wait= service= status=503 bytes=
2012-06-12T14:19:23+00:00 heroku[nginx]: 122.179.134.45 - - [12/Jun/2012:14:19:23 +0000] "GET / HTTP/1.1" 503 601 "-" "Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20100101 Firefox/12.0" myapp1101.heroku.com
2012-06-12T14:27:35+00:00 app[web.1]: !! Unexpected error while processing request: can't modify frozen array
2012-06-12T14:27:35+00:00 heroku[router]: Error H13 (Connection closed without response) -> GET sheets-vip.heroku.com/ dyno=web.1 queue= wait= service= status=503 bytes=
2012-06-12T14:27:35+00:00 heroku[nginx]: 122.179.134.45 - - [12/Jun/2012:14:27:35 +0000] "GET / HTTP/1.1" 503 601 "-" "Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20100101 Firefox/12.0" myapp1101.heroku.com
+5
source share
1 answer

This error occurs when something deep depending on your application explodes. For example, we saw this error when the incoming request was huge (i.e. This is a JSON document at + 100 K). We were able to fix this by setting:

Rack::Utils.key_space_limit = some appropriate value

That is, H13 was a b / c Rack error. Try to increase the registration in your application, as this may indicate an error (which we ultimately nullify in the Rack key space limit).

+2
source

More articles:


All Articles