Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 71051 invoked from network); 25 Jan 2008 18:41:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Jan 2008 18:41:07 -0000 Received: (qmail 42481 invoked by uid 500); 25 Jan 2008 18:40:56 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 42448 invoked by uid 500); 25 Jan 2008 18:40:56 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 42437 invoked by uid 99); 25 Jan 2008 18:40:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jan 2008 10:40:56 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [63.82.107.6] (HELO red.amberpoint.com) (63.82.107.6) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jan 2008 18:40:43 +0000 Received: from [127.0.0.1] (bpendleton-desk.edgility.com [10.10.12.116]) by red.amberpoint.com (8.14.0/8.12.11) with ESMTP id m0PIeWmr000222 for ; Fri, 25 Jan 2008 10:40:32 -0800 (PST) Message-ID: <479A2D20.7040000@amberpoint.com> Date: Fri, 25 Jan 2008 10:40:32 -0800 From: Bryan Pendleton User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Derby Discussion Subject: Re: How to clean the derby cache References: <479A2758.8060405@lsd.ufcg.edu.br> <479A27EE.9020201@lsd.ufcg.edu.br> In-Reply-To: <479A27EE.9020201@lsd.ufcg.edu.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org > I suspect that the database cache is returning this old information. Perhaps the transaction which is updating the information has not yet committed, and the transaction which is trying to fetch the information is running at READ COMMITTED isolation level. In that case, the database will happily return the old information. See: http://db.apache.org/derby/docs/10.3/devguide/cdevconcepts15366.html thanks, bryan