Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 93747 invoked from network); 15 Sep 2009 22:23:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Sep 2009 22:23:30 -0000 Received: (qmail 93154 invoked by uid 500); 15 Sep 2009 22:23:30 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 93077 invoked by uid 500); 15 Sep 2009 22:23:30 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 93067 invoked by uid 99); 15 Sep 2009 22:23:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Sep 2009 22:23:30 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=NORMAL_HTTP_TO_IP,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of adam.kocoloski@gmail.com designates 209.85.221.196 as permitted sender) Received: from [209.85.221.196] (HELO mail-qy0-f196.google.com) (209.85.221.196) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Sep 2009 22:23:17 +0000 Received: by qyk34 with SMTP id 34so3610203qyk.12 for ; Tue, 15 Sep 2009 15:22:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:x-mailer :mime-version:subject:date:references; bh=o7HvdkjjuqmlWDzGUXifLdtXyZWsXJfZJXlucklMeA4=; b=iQ3h2BRt+yxyAbujuYxTPuyrGMTgZMR/Nw9xBqJwepseX0GutsyFPrTTHjDvzJzjXt SHVClCdVCHNisG/o/n32fuUd43DLEXGftWrQytWgTTH6YVdS9nB5jFgB/wWSo3SVRmPh fqjIHKNoIe/ypQBS8mscNH90rUXzw+gKtlvYY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type :content-transfer-encoding:x-mailer:mime-version:subject:date :references; b=U6HvnZo+L2+t2tPLdChOqzSQs4lHZvuon/AUnH7RwiE9zCpw9T/j4epX5oLkpoteBm U7BfN+D2gVIL/rZJrbntH1zaI94Utwj5H+CqrCvsNBMuaWg9FV7IwJsGoyuojWz/cLi4 JYQbYz1dzzywKTh6KRTDlU3QApYDGD7KP8JYI= Received: by 10.224.32.204 with SMTP id e12mr6811897qad.256.1253053376287; Tue, 15 Sep 2009 15:22:56 -0700 (PDT) Received: from ?10.90.78.127? (mobile-166-137-135-140.mycingular.net [166.137.135.140]) by mx.google.com with ESMTPS id 4sm126873qwe.45.2009.09.15.15.22.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 15 Sep 2009 15:22:55 -0700 (PDT) Message-Id: From: Adam Kocoloski To: "dev@couchdb.apache.org" In-Reply-To: <1713038414.1253052717504.JavaMail.jira@brutus> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (7A400) Mime-Version: 1.0 (iPhone Mail 7A400) Subject: Re: [jira] Commented: (COUCHDB-504) HTTP/1.1 keep alive fails with AB Date: Tue, 15 Sep 2009 18:22:27 -0400 References: <1713038414.1253052717504.JavaMail.jira@brutus> X-Virus-Checked: Checked by ClamAV on apache.org There's no keep-alive in HTTP/1.0 ... Sent from my iPhone On Sep 15, 2009, at 6:11 PM, "Paul Joseph Davis (JIRA)" wrote: > > [ https://issues.apache.org/jira/browse/COUCHDB-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755734#action_12755734 > ] > > Paul Joseph Davis commented on COUCHDB-504: > ------------------------------------------- > > http://code.google.com/p/couchdb-python/issues/detail?id=85 > > Looks like this could be related. > >> HTTP/1.1 keep alive fails with AB >> --------------------------------- >> >> Key: COUCHDB-504 >> URL: https://issues.apache.org/jira/browse/COUCHDB-504 >> Project: CouchDB >> Issue Type: Bug >> Components: HTTP Interface >> Affects Versions: 0.10 >> Environment: Trunk >> Reporter: Paul Joseph Davis >> Assignee: Paul Joseph Davis >> Priority: Blocker >> >> Reported on dev@ >> On Tue, Sep 15, 2009 at 3:33 PM, thomas hallaran >> wrote: >>> Hi all, >>> We are using couchdb in production and have come across what >>> appears to be a >>> bug in the HTTP implementation. Apparently http keep alive >>> requests are not >>> correctly supported by couchdb. >>> >>> This problem has been verified for both couchdb .10 a running on >>> ubuntu >>> with erlang 13.b1 and couchdb .91 running on osx. We have also >>> reproduced >>> it with multiple http clients, the apache hc java client, curl and >>> ab. >>> >>> To Reproduce: ab -v 4 -k -n1 >>> http://localhost:5984/{COUCHDB_GET_ENDPOINT}>> >times >>> out. If you add more requests for ab to do (-n4 or something) you >>> will >>> see that rather than reusing the connection, each keepalive >>> request times >>> out and then the connection is reopened and the request made. >> And I've verified: >> $ svn up >> #snipped >> Updated to revision 815457. >> $ ./bootstrap && ./configure && make dev >> #snipped >> $ ./utils/run >> Apache CouchDB 0.11.0a815457 (LogLevel=info) is starting. >> Apache CouchDB has started. Time to relax. >> # In second terminal >> $ curl -X PUT http://127.0.0.1:5984/test_fu >> {"ok":true} >> $ curl -X PUT -d '{"stuff": "here"}' http://127.0.0.1:5984/test_fu/beer >> {"ok":true,"id":"beer","rev":"1-9782357dd8b8d18d94843686e510ec92"} >> $ ab -v 4 -k -n1 http://127.0.0.1:5984/test_fu/beer >> This is ApacheBench, Version 2.3 <$Revision: 655654 $> >> Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ >> Licensed to The Apache Software Foundation, http://www.apache.org/ >> Benchmarking 127.0.0.1 (be patient)...INFO: POST header == >> --- >> GET /test_fu/beer HTTP/1.0 >> Connection: Keep-Alive >> Host: 127.0.0.1:5984 >> User-Agent: ApacheBench/2.3 >> Accept: */* >> --- >> LOG: header received: >> HTTP/1.0 200 OK >> Server: CouchDB/0.11.0a815457 (Erlang OTP/R13B) >> Etag: "1-9782357dd8b8d18d94843686e510ec92" >> Date: Tue, 15 Sep 2009 19:44:36 GMT >> Content-Type: text/plain;charset=utf-8 >> Content-Length: 74 >> Cache-Control: must-revalidate >> {"_ >> id" >> :"beer","_rev":"1-9782357dd8b8d18d94843686e510ec92","stuff":"here"} >> LOG: Response code = 200 >> apr_poll: The timeout specified has expired (70007) > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. >