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=AWL,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 D7DDD1F726 for ; Mon, 14 Jan 2013 15:49:02 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id EF6CE2E097; Mon, 14 Jan 2013 15:49:02 +0000 (UTC) X-Original-To: mongrel-unicorn@rubyforge.org Delivered-To: mongrel-unicorn@rubyforge.org Received: from mail-wg0-f48.google.com (mail-wg0-f48.google.com [74.125.82.48]) by rubyforge.org (Postfix) with ESMTP id 6A42B2E076 for ; Mon, 14 Jan 2013 15:48:55 +0000 (UTC) Received: by mail-wg0-f48.google.com with SMTP id 16so1171365wgi.27 for ; Mon, 14 Jan 2013 07:48:53 -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=w9JyWD/Kp7bhkixLwA8/a90B02Ni56hQEuXqiICI6SU=; b=JGBOE1qWOaRIEs6JxKeJDE0LmJ43YHdGrJIxN8WB+xVzvyjQCVnAoEajqTB6nbAuDm PS7E/Uy6Ho5pBK5GbhQQRq29GZriW6mdzb7yivGWpZO4Qx/5j+sPNFUJa0b7aS0IvQjt p/d3NWPboH2+Hg2xAKpBOx8dGI9FKsaJu2YNk6Uijap4ueHFfQxCiVSKST/9Wi8HyX74 CQ9b0COOwrycfmfCEwRKhtVucgplpP90Ii8X/40gEy3XkLwUTaiCX6w3zmExUYNH9hKF aexkXNgYhINlQ8R1J4R41RZO4hIQY22nHwhYzLVv3sEerC84ZKbaZKLfLegtf+Ki+Fqf 6Qqg== X-Received: by 10.180.109.195 with SMTP id hu3mr13083879wib.31.1358178168829; Mon, 14 Jan 2013 07:42:48 -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 s10sm14579212wiw.4.2013.01.14.07.42.47 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Jan 2013 07:42:48 -0800 (PST) From: Manuel Palenciano Guerrero Subject: Increassing timeouts Message-Id: Date: Mon, 14 Jan 2013 16:42:41 +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 of the apps talking 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 Palenciano _______________________________________________ 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