Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 65838 invoked from network); 23 Jan 2006 11:16:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Jan 2006 11:16:36 -0000 Received: (qmail 72460 invoked by uid 500); 23 Jan 2006 11:15:25 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 72193 invoked by uid 500); 23 Jan 2006 11:15:22 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 72162 invoked by uid 99); 23 Jan 2006 11:15:21 -0000 X-ASF-Spam-Status: No, hits=-10.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO [127.0.0.1]) (209.237.227.194) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jan 2006 03:15:19 -0800 Message-ID: <43D4BB5F.4060202@apache.org> Date: Mon, 23 Jan 2006 12:17:51 +0100 From: Carsten Ziegeler User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: setup() called twice in one request References: <200601191901.58102.rassy@math.tu-berlin.de> <200601201413.01962.rassy@math.tu-berlin.de> <43D495F2.2080401@apache.org> <200601231151.31529.rassy@math.tu-berlin.de> In-Reply-To: <200601231151.31529.rassy@math.tu-berlin.de> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Tilman Rassy schrieb: > On Monday 23 January 2006 09:38, Carsten Ziegeler wrote: >> Tilman Rassy wrote: >>> Hello, >>> >>> On Thursday 19 January 2006 23:43, Joerg Heinicke wrote: >>>> On 19.01.2006 19:01, Tilman Rassy wrote: >>>>> we discovered that the setup() method of a custom generator is sometimes >>>>> called twice in one request. >>>> Are you sure that it is only one request. For example using the Acrobat >>>> Reader in IE results in two requests. >>> I'm quite sure that it is the same request and the the same generator >>> instance - we have very detailed logging. Here is an exceprt from the >>> logs: >>> >>> ------------ log except start ----------- >>> >>> >> Strange, what about the generate() method? When is that one called? >> Twice as well? > > In the case of the request with the two setup() calls, it is not called at > all. Probably the response is taken from the cache. In other cases, when it > is called, it is called only once. > > One thing I should mention is that in all cases the response is not corrupted. > What we see in the browser is exactly what we expect. > >> Now, the best thing would be if you could provide a reproducable test >> case for us. > > Yes, I will try to create one. However, since our system contains a lot of > code and data, it may take a little time to extract a testcase from it. > Sure :) Can you provide a stack trace for the two calls of the setup() method, so we can see from where this method is called. Thanks Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/