From dev-return-18483-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Thu Feb 03 17:14:28 2011 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 67292 invoked from network); 3 Feb 2011 17:14:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Feb 2011 17:14:28 -0000 Received: (qmail 17485 invoked by uid 500); 3 Feb 2011 17:14:28 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 17321 invoked by uid 500); 3 Feb 2011 17:14:26 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 17313 invoked by uid 99); 3 Feb 2011 17:14:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Feb 2011 17:14:25 +0000 X-ASF-Spam-Status: No, hits=3.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of curtisr7@gmail.com designates 74.125.83.46 as permitted sender) Received: from [74.125.83.46] (HELO mail-gw0-f46.google.com) (74.125.83.46) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Feb 2011 17:14:21 +0000 Received: by gwj20 with SMTP id 20so579516gwj.33 for ; Thu, 03 Feb 2011 09:14:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=nIwP1cLoJoAD2d+xpfp7tgGvtkEOuXMvBiHHgiY9owg=; b=RIvuZVTW7d7VZXPfESG7R0sgw9YKxFfw0gp99p795ebUkoIveInjDbtR6FSW/JL/Ig t05UaugV4vZAUbHruOdAozQPJRwlPzMmvrMzyw1mHYMODEYm5ZUO9A0UkdI2Hh9dPmeM HCo82IonIySDLWLyrgNMESGWUHAJRWkEqnOrk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=qDq5vWT3DL6RcxpTvqE2hQYGgOXR/djp1syB2NUmYRuJ8nMieyO0xZym+IulVslONf cmU5ckMXNzWwmOvQQYNs2MMHCXNPVERReQL/znR/2Ht1/tpToH0sSYQ/IUpfGvs+bvXH Mokc+2LFeWq0ky8mFVGeqFOk9oKnoCLHmerwI= MIME-Version: 1.0 Received: by 10.42.241.132 with SMTP id le4mr13092990icb.356.1296753240086; Thu, 03 Feb 2011 09:14:00 -0800 (PST) Received: by 10.231.32.73 with HTTP; Thu, 3 Feb 2011 09:14:00 -0800 (PST) In-Reply-To: References: Date: Thu, 3 Feb 2011 11:14:00 -0600 Message-ID: Subject: Re: EntityManagerFactory clearing caches on close()? From: Rick Curtis To: dev@openjpa.apache.org Content-Type: multipart/alternative; boundary=20cf30549edf3c9978049b63e4c8 --20cf30549edf3c9978049b63e4c8 Content-Type: text/plain; charset=ISO-8859-1 Alex - Hmmm, by any chance are you using the ehcache plugin? If so, it is probably an issue with the plugin implementation. AFAIK with the built in query cache we don't distribute the QueryCache. Thanks, Rick On Thu, Feb 3, 2011 at 10:58 AM, Alex Snaps wrote: > Hi guys, > I've not investigated that much at the code level yet, but it seems > EntityManagerFactory.close() calls AbstractQueryCache.close() which in > turn calls clearInternal(). As a result a distributed query cache ends > up cleared when a node is shut down. This only seems to happen on the > query cache though. Is it meant that way? If so, does that mean a > query cache shouldn't be clustered? > Thanks, > Alex > > -- > Alex Snaps > Senior Software Engineer - Terracotta > http://twitter.com/alexsnaps > http://www.linkedin.com/in/alexsnaps > --20cf30549edf3c9978049b63e4c8--