From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS33070 50.56.128.0/17 X-Spam-Status: No, score=0.0 required=5.0 tests=FREEMAIL_FROM,T_DKIM_INVALID shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: archivist@yhbt.net Delivered-To: archivist@dcvr.yhbt.net Received: from rubyforge.org (50-56-192-79.static.cloud-ips.com [50.56.192.79]) by dcvr.yhbt.net (Postfix) with ESMTP id 083FA1F73F for ; Wed, 16 Jan 2013 15:22:46 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 6473B2E09A; Wed, 16 Jan 2013 15:22:45 +0000 (UTC) X-Original-To: mongrel-unicorn@rubyforge.org Delivered-To: mongrel-unicorn@rubyforge.org Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) by rubyforge.org (Postfix) with ESMTP id 1B25F2E096 for ; Wed, 16 Jan 2013 15:17:19 +0000 (UTC) Received: by mail-wg0-f54.google.com with SMTP id fg15so920290wgb.21 for ; Wed, 16 Jan 2013 07:17:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version:x-mailer; bh=LQcCw6r3SvEplwBg5icdL5R/7f+GuKbLswI+zHnvVe4=; b=bHtbXcsqsXUfMYCQh6UQtxHk7NeTe+T9bvcm85fMv8Q9KSTcv9yxPla9RA9TX3fazq 7+d+hLo93X6XImdxSRoe0FMSAJs5+MqeHTUhi2ceLlO47PbIsE+8fV+cd7nQuvHYtefa lZnKIXa5FvatgSEor+EvxcGpYJ3THfMijys8svcrL23/9OQOyCNfP2BE4XpiL2rw2UkG 4AtI8xNrHvrB/sOr1LzCSe2rVsmkUDoEBsooEZGqx/3JWoc1qEbtpEIGA8CNs29eAZjL VeuNjBUczPt5lVUx7kVGquhuNDNcfOzTQsOueoGHz0uy6ceBiiwkk/AP5MA9UDE80WkA tptA== X-Received: by 10.194.77.13 with SMTP id o13mr2798064wjw.58.1358349438442; Wed, 16 Jan 2013 07:17:18 -0800 (PST) Received: from [192.168.1.200] (188.227.23.95.dynamic.jazztel.es. [95.23.227.188]) by mx.google.com with ESMTPS id s10sm9550961wiw.4.2013.01.16.07.17.16 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Jan 2013 07:17:17 -0800 (PST) From: Manuel Palenciano Guerrero Subject: Increassing timeouts Message-Id: Date: Wed, 16 Jan 2013 16:17:10 +0100 To: "mongrel-unicorn@rubyforge.org list" Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) X-BeenThere: mongrel-unicorn@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mongrel-unicorn-bounces@rubyforge.org Errors-To: mongrel-unicorn-bounces@rubyforge.org Hello there We use Unicorn in all of our production/staging web-apps, and we are very happy with it. But we also have one app which talks to a web-service via SOAP, and this web-service now takes longer than usual processing requests. To solve this situation we have increased the time-outs for unicorn and nginx (proxy_read_timeout and proxy_connect_timeout) from 30 to 120, and everything works fine this way (although I don't like it). My question is: having increased the time-out to 120 means this app is now considered slow (or sleepy) and should be run by Rainbow ? or is 120 still ok for Unicorn ? Thanks in advance ! Manuel P. _______________________________________________ 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