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 will return a response in 50ms and then, 5 seconds later, heroku will say the dyno has timed out. It's really odd. Any ideas? Scott Scott Messinger *|* Founder, Common Curriculum *|* (360) 904.5947 *|* @scottmessinger *|* www.commoncurriculum.com On Fri, Jan 25, 2013 at 10:01 AM, Daniel Doubrovkine <[email protected]>wrote: > 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 somewhere at 20 seconds or so. It will raise an exception > after 20s of a request and you might get a more useful stack. > > > On Fri, Jan 25, 2013 at 9:39 AM, Scott Messinger < > [email protected]> wrote: > >> 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 timeout) -> GET *****.herokuapp.com/ dyno=web.1 >>> queue= wait= service=30000ms status=503 bytes=0 CRIT >>> >>> Random request timeout. Monitoring this in New relic I see that after >>> this kind of error my app is going down for 1 hour or more and then start >>> work fine again. >>> >>> I must say that I'm on devellopment so I run the app on a single dyno.(I >>> tried to scale up to 3 but nothing changed). >>> althought I'm the only visitor (testor) of my app so there is no way >>> that I drawning my dyno under requests... >>> >>> I really don't understand what is going on and the error message are not >>> helping neither is google.... >>> >>> I like heroku very much but this is critical and I'm starting to doubt >>> wether heroku is a fine solution for production. >>> >>> Any kind of help would be very much appreciated. >>> >>> >>> sebastien. >>> >>> -- >> -- >> You received this message because you are subscribed to the Google >> Groups "Heroku" group. >> >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/heroku?hl=en_US?hl=en >> >> >> >> > > > > -- > > dB. | Moscow - Geneva - Seattle - New York > dblock.org <http://www.dblock.org> - > @dblockdotorg<http://twitter.com/#!/dblockdotorg> > > -- > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en_US?hl=en > > > > -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
