Hi Sebastien,
On our site, we're seeing the same errors without any perceptible cause.
Did you find a fix or a cause for the H12 errors you were seeing?
Scott
On Wednesday, June 27, 2012 10:49:38 AM UTC-4, Sébastien VIAN wrote:
Hi i'm having the same issue basically.
Error H12 (Request
Okay! Tom Lane has now fixed this and future Postgres releases will not
exhibit this behaviour. The commit should land shortly. Thanks for the
report!
On Mon, Jan 21, 2013 at 11:04 PM, Peter van Hardenberg p...@heroku.comwrote:
Thanks for the extra reply Nickolay. I think I came up with a
Every single one of these has been a problem with our application. I
suggest using NewRelic, which will instrument the requests and show you
where you're spending time during those requests that time out.
Another idea is to use the https://github.com/kch/rack-timeout gem and set
the timeout
Hi Daniel,
Thanks for the response. We've been using the rack-timeout gem (timeout of
10 seconds) and have been using NewRelic. We can't find any indication that
our app is taking more than 100ms to respond.
Granted, this seems odd. However, the logs and new relic tell the same
story: a dyno
Assuming you have more than 1 dyno, the dynos are always up.
Then, is this a Rails app? Thin? Unicorn? Heroku round-robins requests, so
it's possible that there're 2 requests coming at the same time, and both go
to the same dyno. Then your app has a bug where the second request isn't
being
