Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 234DFEA0B for ; Sat, 16 Feb 2013 06:15:18 +0000 (UTC) Received: (qmail 84443 invoked by uid 500); 16 Feb 2013 06:15:17 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 84322 invoked by uid 500); 16 Feb 2013 06:15:16 -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 84259 invoked by uid 99); 16 Feb 2013 06:15:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Feb 2013 06:15:14 +0000 Date: Sat, 16 Feb 2013 06:15:14 +0000 (UTC) From: "Christopher Bonhage (JIRA)" To: dev@couchdb.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (COUCHDB-1651) Server responds 400 "Exceeded rewrite recursion limit" indefinitely MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COUCHDB-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579726#comment-13579726 ] Christopher Bonhage commented on COUCHDB-1651: ---------------------------------------------- Paul, I think you'll find the issue completely resolved with my patch above. The '1651-recursive-rewrite-leak' branch solves the symptom of the error being unrecoverable, but does not address the root cause of the error, which is that re-used processes are being treated as recursed rewrites. > Server responds 400 "Exceeded rewrite recursion limit" indefinitely > ------------------------------------------------------------------- > > Key: COUCHDB-1651 > URL: https://issues.apache.org/jira/browse/COUCHDB-1651 > Project: CouchDB > Issue Type: Bug > Components: HTTP Interface > Reporter: Paul Frazee > Attachments: resolve_spurious_rewrite_limit_errors.patch > > > Running 1.2.1 on Windows 7 as a service. > hosts file includes "127.0.0.1 grimwire.local" > CouchDB conf includes vhosts entries: > grimwire.local:5984 /grimwire/_design/grimwire/_rewrite > grimwire.local:5984/local /grimwire/_design/local/_rewrite > 'grimwire' design doc rewrites: > [ > { > "from": "", > "to": "index.html", > "method": "GET" > }, > { > "from": "*", > "to": "*" > } > ] > 'local' design doc rewrites: > [ > { > "from":"", > "to":"index.html", > "method":"GET" > }, > { > "from":"/posts", > "to":"_list/wallpost/wallpost-by-created_at", > "method":"GET" > }, > { > "from":"/posts", > "to":"_update/wallpost", > "method":"POST" > }, > { > "from":"/posts/:id", > "to":"_show/wallpost/:id", > "method":"GET" > }, > { > "from":"/posts/:id", > "to":"_update/wallpost/:id", > "method":"PUT" > }, > { > "from":"*", > "to":"*" > } > ] > Problem: > The requests work as expected for some unknown period, then begin to respond with a 400 status and the "Exceeded rewrite recursion limit" error message. Changing the rewrites rules for both applications, including setting them to empty arrays, had no effect. > The problem was solved by restarting the CouchDB service. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira