unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Alex Sharp <ajsharp@gmail.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Timeout callback
Date: Mon, 26 Sep 2011 12:04:04 -0700	[thread overview]
Message-ID: <74BCCFBDF6C4414382DC540C16B2301B@gmail.com> (raw)
In-Reply-To: <CADuahaAQSQ7DQymSyCwtw_6+vpgT3eR8uUB1muzYrO=520jE6A@mail.gmail.com>

On Sunday, September 25, 2011 at 11:06 PM, Christopher Bailey wrote:
> What we wound up doing, which may or may not work for you, is to put
> an explicit Timeout wrapper around the code we knew caused this (we
> are lucky and knew a specific API call/controller action that was
> getting the timeouts). e.g. wrap with:
> 
>  Timeout::timeout(...) do
> 
> This wound up actually being a far better solution for us, because our
> mobile clients that call this API timeout the HTTP request at 20
> seconds anyway, so it was pointless to even get to 60. So, we now
> have a far better solution, one where we can time it out ourselves,
> handle the exception, and log the timeout/problem (e.g. we create a
> Zendesk ticket, etc.). Anyway, figured I'd mention that in case it
> could work in your case as well...
Great, thanks for sharing.

- Alex 


_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying

  reply	other threads:[~2011-09-26 19:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-26  1:24 Timeout callback Alex Sharp
2011-09-26  1:42 ` Eric Wong
2011-09-26  6:06   ` Christopher Bailey
2011-09-26 19:04     ` Alex Sharp [this message]
2011-09-26 19:02   ` Alex Sharp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=74BCCFBDF6C4414382DC540C16B2301B@gmail.com \
    --to=ajsharp@gmail.com \
    --cc=mongrel-unicorn@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).