I'm not sure then. If it is just happening sporadically can you contact support.heroku.com please?
-- Richard Schneeman http://heroku.com @schneems Sent from the road On Monday, April 2, 2012 at 1:54 PM, kowsik wrote: > Neil, > Just the odd timeouts. > > Thanks, > > K. > --- > http://blitz.io > @k0ws1k > > On Mon, Apr 2, 2012 at 11:39 AM, Neil Middleton > <neil.middle...@gmail.com> wrote: > > Kowsik, > > > > Are you seeing long queues or just the odd timeout? > > > > -Neil > > > > Sent with my tiny little Internet device. > > > > On Monday, 2 April 2012 at 19:22, Richard Schneeman wrote: > > > > I do you have rack cache on your app? I recommend setting that up and using > > memcache for the meta store. Also setting your expire headers on static > > assets to a far future date. That should help with timeouts especially with > > static assets. You can also try using a CDN but that is quite a bit more > > work for sinatra > > https://devcenter.heroku.com/articles/error-codes#h12__request_timeout > > > > You can also consider increasing your dyno count. What web server are you > > using? > > > > -- > > Richard Schneeman > > http://heroku.com > > @schneems > > > > On Monday, April 2, 2012 at 12:27 PM, kowsik wrote: > > > > We are seeing sporadic H12 Request Timeout's in the logs, even for > > static assets: > > > > 2012-04-02T17:25:06+00:00 heroku[router]: Error H12 (Request timeout) > > -> GET blitz.io/images/logo.png dyno=web.1 queue= wait= > > service=30000ms status=503 bytes=0 > > > > This is a Sinatra app on the Cedar stack. Given that this is a static > > asset, I'm pretty sure it's not our code or our database that's > > causing the problem. > > > > Any ideas? > > > > Thanks, > > > > K. > > --- > > http://blitz.io > > @k0ws1k > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to heroku@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/heroku?hl=en. > > > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to heroku@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/heroku?hl=en. > > > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to heroku@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/heroku?hl=en. > > > > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to heroku@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.